It could happen that I get it completely wrong and we are seeing an
environmental issue.
As the revert PR also failed. I see some nb-javac related warnings in
the failed job logs. Though I do not know if it is walid or not
regarding to some test case. It seems to happen with the
java/java.source.base module
[junit] WARNING [org.netbeans.core.startup.NbEvents]: The extension
/home/travis/build/apache/netbeans/nbbuild/netbeans/ide/modules/ext/jcodings-1.0.18.jar
may be multiply loaded by modules:
[/home/travis/build/apache/netbeans/nbbuild/netbeans/ide/modules/org-netbeans-modules-textmate-lexer.jar,
/home/travis/build/apache/netbeans/nbbuild/netbeans/ide/modules/org-netbeans-libs-bytelist.jar];
see:
http://www.netbeans.org/download/dev/javadoc/org-openide-modules/org/openide/modules/doc-files/classpath.html#class-path
[junit] Warning - could not install some modules:
[junit] org.netbeans.modules.java.source.nbjavac - No module providing
the capability org.netbeans.modules.nbjavac could be found.
[junit] Warning - could not install some modules:
[junit] Java Source nb-javac Bridge - No module providing the
capability org.netbeans.modules.nbjavac could be found.
On 7/1/19 12:22 AM, Laszlo Kishalmi wrote:
Created https://github.com/apache/netbeans/pull/1345 for it.
On 6/30/19 11:52 PM, Geertjan Wielenga wrote:
Sounds good to me. We need to be careful with what new checks we
introduce
when we’re in release mode.
Gj
On Mon, 1 Jul 2019 at 05:25, Laszlo Kishalmi <[email protected]>
wrote:
The following commit:
https://github.com/apache/netbeans/commit/6532336e9e4b826405fda82e15972d5a92a4cc4e
caused Travis CI to fail, ever since it is committed.
It says "Travis, Run ide modules tests" and includes a new job which
runs tests on Travis, which is eventually fail since it's introduction.
First, I agree with the intent. It is really good to have additional
quality gates.
It seems this check fails since it has been committed into master.
Telling the truth, without a good report/summary it is really hard to
tell which test fails. Also the corresponding Jenkins job
https://builds.apache.org/job/netbeans-linux is actually seems to be
fine.
Nevertheless we are in release mode, so every PR is checked more
thoroughly whether it can go to master for 11.1 or not. It creates
confusion for committers and for the RM as well. So the timing is quite
ill.
I'd disable that job for now and reintroduce when the 11.2 window would
be open. Though before reintroduction a good failed test summary has to
be produced.
Laszlo Kishalmi
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
