-DreuseForks=false indeed lets the problem go away. Now we need to find out where this side effect is coming from.
LieGrue, strub > Am 16.02.2018 um 14:31 schrieb Romain Manni-Bucau <[email protected]>: > > Hi Mark, can't reproduce it but used a johnzon 1.1.6 created from the > 1.1.7-SNAPSHOT since the tag is not pushed on asf yet. Not sure it has an > impact or if it is the test order which is responsible of it.Maybe try > forcing reuseFork=false in surefire to validate this hypothesis > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > 2018-02-16 13:56 GMT+01:00 Mark Struberg <[email protected]>: > >> no worries, we first have to fix a seemingly random test failure in MW >> anyway >> >> Tests in error: >> MultipartTest.configBinding:51 » ResponseProcessing Problem with reading >> the d... >> >> happens only when this test is executed with all other tests. >> Wenn running the test alone all is green. >> >> Anyone want's to take that up? >> I'm offline for the next few hours now. >> >> LieGrue, >> strub >> >> >>> Am 16.02.2018 um 13:49 schrieb Romain Manni-Bucau <[email protected] >>> : >>> >>> +1 >>> >>> Side note: can you ensure it is either not deployed or staging repo are >> in >>> the pom to not break early consumers please? >>> >>> >>> Le 16 févr. 2018 13:19, "Mark Struberg" <[email protected]> a >>> écrit : >>> >>>> will roll a MW release in the afternoon. >>>> >>>> Currently testing the updates to the staged versions. >>>> >>>> LieGrue, >>>> strub >>>> >>>> >> >>
