Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-releng-dev] Official tests vs Maven tests

Hi,

 

In official test run we run the tests using ant. Here are the steps

  1. Extract SDK
  2. Select plugin to run
  3. Install its dependencies
  4. Run default job from test.xml of the test plugin

 

I am not so sure about how the SDK product is created in the maven environment for test purposes. I believe we use surefire plugin to run the tests. There must be a change in the way surefire is running the tests.

 

Thanks and Regards,

Sravan

 

Sravan Kumar Lakkimsetti

IBM India Pvt Ltd,

Embassy Golf Links Business Park, D Block,

Off Indiranagar-Kormangla Inner Ring Road,

Bangalore - 560071, India

Phone: 91-80-41776858

 

From: Mickael Istria <mistria@xxxxxxxxxx>
Sent: Monday, March 04, 2019 2:37 PM
To: Eclipse platform release engineering list. <platform-releng-dev@xxxxxxxxxxx>
Subject: [platform-releng-dev] Official tests vs Maven tests

 

Hi all,

 

With https://bugs.eclipse.org/bugs/show_bug.cgi?id=541415 , it appeared that there can be major divergence between what we can see when running tests locally, on Gerrit and in the "official" tests.

It seems for example that programatically generated SWT events can be ignored on official test execution when they work fine locally or on CI.

Does anyone have a clue or why this happens and how we can remediate?

 

I may have one, that I experience locally: I'm using Xephyr and mutter (a bit different from what's used on Jenkins, but still it's a similar stack), and I see the one of them seems to have an energy saving strategy that makes that after some time, screen turns black, and when this happens, some tests do fail.

Could it be also something that happen when running the big test suite?

 

Cheers,

--

Mickael Istria

Eclipse IDE developer, for Red Hat Developers



Back to the top