Might be better to just discuss problems in this thread before voting -1 so we can understand the severity of the problem. I want us to have a philosophy that problems have to be pretty severe or a bad break of something that worked before in order to hold up a release. We want an efficient release process and anything that can wait for the next release should.
Your console output is rather strange, and I believe this test has passed on Windows on build.a.o, so it may not be a major problem in the source package itself. The interesting part of your console output is this: Running aa.AAAMavenTestExternc ... Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.881 sec - in aa.AAAMavenTestExternc Running aa.AAMavenTestSWCs ... C:\temp\royale-rc1\apache-royale-0.9.0-src\royale-compiler\compiler\target\ compile-as-config.xml(30): col: 0 Error: unable to open 'C:\temp\royale-rc1\apache-royale-0.9.0-src\royale-compiler\compiler-extern c\target\js.swc'. ... 290655 bytes written to C:\temp\royale-rc1\apache-royale-0.9.0-src\royale-compiler\compiler-externc \target\js.swc in 7.039 seconds Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.73 sec <<< FAILURE! - in aa.AAMavenTestSWCs What is interesting is that aa.AAAMavenTestExternc generates a js.swc file that aa.AAMavenTestSWCs doesn't find so it fails. But somehow aa.AAMavenTestSWCs is being run before the console output shows that 290655 bytes were written out as js.swc! I don't think we've configured the tests to run in parallel. Can you investigate to see if we are running tests in parallel or if there is something else delaying the output of the js.swc? I believe I have seen Windows anti-virus programs screw up the timing of when things get written out. Thanks, -Alex On 1/8/18, 10:24 PM, "[email protected] on behalf of OmPrakash Muppirala" <[email protected] on behalf of [email protected]> wrote: >As mentioned in the VOTE thread, I had unit tests failing while building >the compiler with Maven. The full console log is available here [1] > >Thanks, >Om > >[1] >https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgist.gith >ub.com%2Fanonymous%2F146e95749626a54dd2a6a2937c9591c0&data=02%7C01%7Caharu >i%40adobe.com%7Cceb80d997c9e471a09f608d55729c251%7Cfa7b1b5a7b34438794aed2c >178decee1%7C0%7C0%7C636510759229586647&sdata=siX7PVVjIeADiZBU1ijtSyY03tJtQ >AyC4L92XzGSQ%2Fk%3D&reserved=0 > >On Mon, Jan 8, 2018 at 10:14 PM, Olaf Krueger <[email protected]> >wrote: > >> I'll try to do test it tonight but I am not sure if I had already use >>maven >> with my current machine... I will check it out. >> >> >3) Place following file template to the folder with your pom.xml [1] >> >> I guess this should be namend as settings-template.xml? >> >> Thanks, >> Olaf >> >> >> >> >> >> -- >> Sent from: >>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-ro >>yale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com >>%7Cceb80d997c9e471a09f608d55729c251%7Cfa7b1b5a7b34438794aed2c178decee1%7C >>0%7C0%7C636510759229586647&sdata=QiF5DrFuBJ8shGp0mEJhqic%2BHIqx4lSHx91Ekh >>WQMGY%3D&reserved=0 >>
