Community
Participate
Working Groups
Master bug for all components to enable their tests during the Tycho build. This will include them into the Gerrit build trigger.
As I understood the discussion in status meeting, after everyone has a chance to try to implement/fix tests to run during the build, then we will change the default in the parent pom. Not sure if the intent was to change the default for M2, or after M2 for M3. So, let me know. Once that default is changed, components should remove explicit enablement of tests, but some will have to add explicit disablement of tests in their component poms. Once that default is changed, I am not sure if during production builds, we should still disable it? (So, we at least get a build, even if a test would fail) or just go ahead and fail whole build, if any test fails? In the past our philosophy has been to "produce a build", in any case, since some teams might be able to "start testing it" even if there is another component that will have to make a fix and re-spin. That's still my preference, but happy to change to "always fail" approach, if there is consensus to do so.
(In reply to David Williams from comment #1) > Once that default is changed, I am not sure if during production builds, we > should still disable it? (So, we at least get a build, even if a test would > fail) or just go ahead and fail whole build, if any test fails? In the past > our philosophy has been to "produce a build", in any case, since some teams > might be able to "start testing it" even if there is another component that > will have to make a fix and re-spin. That's still my preference, but happy > to change to "always fail" approach, if there is consensus to do so. This can be problematic because we have a few tests across different components that are known to fail randomly for unknown reason and it would be bad to fail the whole build because of such test failure.
(In reply to David Williams from comment #1) > Once that default is changed, I am not sure if during production builds, we > should still disable it? (So, we at least get a build, even if a test would > fail) or just go ahead and fail whole build, if any test fails? In the past > our philosophy has been to "produce a build", in any case, since some teams > might be able to "start testing it" even if there is another component that > will have to make a fix and re-spin. That's still my preference, but happy > to change to "always fail" approach, if there is consensus to do so. Well, until we move the official build to Tycho and run our tests, we want to skip the test. Otherwise our build will take double the time. And I agree that we always want to produce the build despite of any test failures.
Untargeting for a specific milestone, since not sure which milestone this will be finished in. (But from the number of open "depends on" bugs it doesn't look like M3).
Isn't it a dup of bug 416904 ?
*** Bug 416904 has been marked as a duplicate of this bug. ***
Most of the projects have their tests enabled. The remaining ones will be done during 4.7.
Lets mark this aggregator bug as fixed. AFAIK most tests are now enabled.
