> On Nov 17, 2020, at 1:50 AM, Jonathan Gallimore > <[email protected]> wrote: > > I kicked off a run of this last night: > https://ci-builds.apache.org/job/Tomee/job/master/10/ - which completed (it > was hanging before), with 38 test failures, looking to be OWB related. The > tests I've looked at so far locally pass ok - I'm wondering if this is > specific to Jenkins, or timing related (as the build went past midnight, > and so old snapshots may be picked up. > > Kicked off another full build on Jenkins, and also a full build locally > (which take about half the time of the CI). I'll report back.
I tried some time ago to set us up in the Apache setup for Jenkins and got failures along with a very not intuitive reactor order. For example, in module order from this build: - https://ci-builds.apache.org/job/Tomee/job/master/10/ This is not a complete summary, but a highlight the most odd ordering I see: Unstable TomEE :: Arquillian Adaptors Parent :: Tests :: Web Profile 29 min ... Success TomEE :: TomEE :: Apache TomEE 1 min 53 sec ... Success TomEE :: Assembly 3.6 sec ... Success TomEE :: Container :: Core The above is the opposite of what I'd expect, which is: - Build the core code (TomEE :: Container :: Core) - Assemble the webapps (TomEE :: Assembly) - Create the Apache TomEE distribution zips (TomEE :: TomEE :: Apache TomEE) - Integration test the zips (TomEE :: Arquillian Adaptors Parent :: Tests :: Web Profile) Instead we have: - Test the zips we haven't built yet - Build the zips from webapps we haven't created yet - Build the webapps from code we haven't compiled yet - Now compile the code It's completely baffling. We get the correct order on our machines and in buildbot. It's just this Jenkins that seems to create such a completely unintelligible result. It's like there is some invisible setting or "optimization" enabled. -David
smime.p7s
Description: S/MIME cryptographic signature
