But does this not answer the question: FYI: > https://builds.apache.org/job/incubator-netbeans-linux/ > and > https://builds.apache.org/job/incubator-netbeans-windows > run platform tests. >
Gj On Wed, Jul 18, 2018 at 1:43 PM, Eirik Bakke <[email protected]> wrote: > Looking at the "last stable build" of incubator-netbeans-linux, this one > reports "no failures", yet has a failure in > org.netbeans.junit.OrderHid.testSnd > (and a few more also in the nbjunit module): > > https://builds.apache.org/job/incubator-netbeans-linux/480 > > Is there somehting special about the nbjunit module that makes Jenkins > ignore test failures there, and only there? (I don't see it in the list of > tests at https://builds.apache.org/job/incubator-netbeans-linux/480/ > testReport/ .) > > These Jenkins builds also omit all the tests in the "ide" cluster, right? > E.g. most of the editor.* modules? When I run tests in editor.lib2 myself, > I get several errors [1]. I'm trying to figure out whether this is due to > my own setup, or whether it's a problem in the codebase itself. > > -- Eirik > [1] All which boil down to "task failed due to: > java.lang.NoClassDefFoundError: > org/netbeans/editor/GuardedDocument", e.g. in org.netbeans.modules.editor. > lib2.highlighting.HighlightingManagerTest . Seems like something I'm > doing wrong with the build--unless there's an error in a static initializer > somewhere. I tried a clean build of the entire incubator-netbeans repo, > both on MacOS and Windows. I used "ant > -Dtest-unit-sys-prop.ignore.random.failures=true > -Dtest.modules=editor.lib2 test" and inspected the output for failures. > > On 7/18/18, 6:24 AM, "Jaroslav Tulach" <[email protected]<mailto: > [email protected]>> wrote: > > FYI: > https://builds.apache.org/job/incubator-netbeans-linux/ > and > https://builds.apache.org/job/incubator-netbeans-windows > run platform tests. > > -jt > > > Dne neděle 15. července 2018 18:47:51 CEST, Eirik Bakke napsal(a): > When I make a pull request on GitHub, there is a nice little checkmark > saying "All checks have passed", with a link to a Travis CI build (e.g. > https://travis-ci.org/apache/incubator-netbeans/builds/ > 395547620?utm_source > =github_status&utm_medium=notification ). > Looking at the raw output of the Travis build, am I correct that this does > _not_ actually run the NetBeans test suite? I searched the console output > and did not find expected messages such as "Tests run:" or "do-junit" or > "[junit]". > Is this also the case for the Jenkins builds at > https://builds.apache.org/view/Incubator%20Projects/job/ > incubator-netbeans-> release ? > Is the current codebase supposed to pass all tests at this point? When I > check out the 9.0-vc3 tag, for instance, both of the following fail with > various errors: > ant commit-validation > ant -Dtest-unit-sys-prop.ignore.random.failures=true test > Are these supposed to work? > -- Eirik > > > > > >
