Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 21/11/2015 13:57, Felix Schumacher wrote: > Am 21.11.2015 um 14:43 schrieb build...@apache.org: >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/645 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: silvanus_ubuntu >> >> Build Reason: The AnyBranchScheduler scheduler named >> 'on-tomcat-commit' triggered this build >> Build Source Stamp: [branch tomcat/trunk] 1715521 >> Blamelist: fschumacher >> >> BUILD FAILED: failed compile_1 > How could my last changes effect > TEST-org.apache.coyote.http2.TestHttp2Section_5_3.NIO.txt? Chances are they didn't. Some of the HTTP/2 tests still are sensitive to timing / ordering. I'm working my way through fixing them but they are often non-trivial because of all the different possible orderings of events. If you (or any one else) want to take a look at this one then go for it. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
Am 21.11.2015 um 14:43 schrieb build...@apache.org: The Buildbot has detected a new failure on builder tomcat-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tomcat-trunk/builds/645 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: silvanus_ubuntu Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-commit' triggered this build Build Source Stamp: [branch tomcat/trunk] 1715521 Blamelist: fschumacher BUILD FAILED: failed compile_1 How could my last changes effect TEST-org.apache.coyote.http2.TestHttp2Section_5_3.NIO.txt? Regards, Felix Sincerely, -The Buildbot - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 07/10/2015 22:54, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/400 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: silvanus_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-commit' > triggered this build > Build Source Stamp: [branch tomcat/trunk] 1707398 > Blamelist: markt > > BUILD FAILED: failed compile_1 The timing fairies *really* don't seem to like me this week. This is 5_3 which has found yet another way to behave I didn't expect. I'm taking yet another look at this now. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 22/09/2015 17:03, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/331 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: silvanus_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-commit' > triggered this build > Build Source Stamp: [branch tomcat/trunk] 1704658 > Blamelist: remm > > BUILD FAILED: failed compile_1 This is an issue with running the resource tests in parallel. Fixing it is on my TODO list. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2015-08-13 16:18 GMT+03:00 : > > The Buildbot has detected a new failure on builder tomcat-trunk while building ASF Buildbot. Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/138 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: silvanus_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-commit' triggered this build > Build Source Stamp: [branch tomcat/trunk] 1695706 > Blamelist: violetagg I'll check this failure. Regards, Violeta > BUILD FAILED: failed compile_1 > > Sincerely, > -The Buildbot > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org >
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 15/06/2015 15:56, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/1383 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: silvanus_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-commit' > triggered this build > Build Source Stamp: [branch tomcat/trunk] 1685591 > Blamelist: markt > > BUILD FAILED: failed compile_1 I need to update ant on the build slave. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 14/04/2015 07:31, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/1134 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: silvanus_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-commit' > triggered this build > Build Source Stamp: [branch tomcat/trunk] 1673408 > Blamelist: markt > > BUILD FAILED: failed compile_1 Just to confirm - this is my fault. It is a side-effect of the SSL config work I started. I'll look into a fix. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
Test org.apache.tomcat.websocket.TestWebSocketFrameClientSSL FAILED (in nio2) - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 24/11/2014 09:17, Mark Thomas wrote: > On 24/11/2014 01:03, build...@apache.org wrote: >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/676 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-commit' >> triggered this build >> Build Source Stamp: [branch tomcat/trunk] 1641296 >> Blamelist: markt >> >> BUILD FAILED: failed compile_1 > > This and the similar failures in Gump look like my fault. The AJP > changes I committed last night appear to have broken NIO. > > I'm working on fixing this. Should be fixed now. The fix is only temporary. A proper fix will follow as part of the connector refactoring. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 24/11/2014 01:03, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/676 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-commit' > triggered this build > Build Source Stamp: [branch tomcat/trunk] 1641296 > Blamelist: markt > > BUILD FAILED: failed compile_1 This and the similar failures in Gump look like my fault. The AJP changes I committed last night appear to have broken NIO. I'm working on fixing this. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2014-08-19 0:58 GMT+04:00 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/379 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1618688 > Blamelist: kkolinko,markt > > BUILD FAILED: failed compile_1 stdio says: [junit] Running org.apache.jasper.compiler.TestCompiler (...) (Tomcat messages, using NIO2 connector...) [junit] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 56.974 sec [junit] Test org.apache.jasper.compiler.TestCompiler FAILED So the failures count is zero, errors count is zero, but JUnit reported the test as failure. I think there is no thing for us to look there. There should have been something else happening on that server to cause the test to run for 57 seconds. In my 8.0.9 testing this test execution time is in 10-14 seconds range for all 4 connectors. The other two runs of the same test (BIO, NIO) completed in 16 seconds. The logs for that test run: http://ci.apache.org/projects/tomcat/tomcat8/logs/1618688/ Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
There was still a test failure with the TestStuckThreadDetectionValve in build 99. But I really don't understand the failure, there's no error in the logs : Here is the extract from http://ci.apache.org/builders/tomcat-trunk/builds/99/steps/compile_1/logs/stdio [junit] Running org.apache.catalina.valves.TestStuckThreadDetectionValve [junit] 21-May-2014 17:47:58.088 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-1"] [junit] 21-May-2014 17:47:58.115 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Tomcat [junit] 21-May-2014 17:47:58.115 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.9-dev [junit] 21-May-2014 17:47:58.607 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-127.0.0.1-auto-1-43485"] [junit] 21-May-2014 17:48:02.602 WARNING [ContainerBackgroundProcessor[StandardEngine[Tomcat].StandardHost[localhost].StandardContext[]]] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread "http-nio-127.0.0.1-auto-1-exec-1" (id=19) has been active for 2,918 milliseconds (since 5/21/14 5:47 PM) to serve the same request for http://localhost:43485/myservlet and may be stuck (configured threshold for this StuckThreadDetectionValve is 2 seconds). There is/are 1 thread(s) in total that are monitored by this Valve and may be stuck. [junit] java.lang.Throwable [junit] at java.lang.Thread.sleep(Native Method) [junit] at org.apache.catalina.valves.TestStuckThreadDetectionValve$StuckingServlet.doGet(TestStuckThreadDetectionValve.java:153) [junit] at javax.servlet.http.HttpServlet.service(HttpServlet.java:618) [junit] at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) [junit] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) [junit] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) [junit] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219) [junit] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) [junit] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:503) [junit] at org.apache.catalina.valves.StuckThreadDetectionValve.invoke(StuckThreadDetectionValve.java:208) [junit] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:136) [junit] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:78) [junit] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) [junit] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:526) [junit] at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1033) [junit] at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:652) [junit] at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:222) [junit] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1565) [junit] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1522) [junit] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [junit] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [junit] at java.lang.Thread.run(Thread.java:722) [junit] [junit] 21-May-2014 17:48:05.789 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-127.0.0.1-auto-1-43485"] [junit] 21-May-2014 17:48:05.790 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service Tomcat [junit] 21-May-2014 17:48:05.807 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-1-43485"] [junit] 21-May-2014 17:48:05.809 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-1-43485"] [junit] 21-May-2014 17:48:05.832 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-2"] [junit] 21-May-2014 17:48:05.864 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Tomcat [junit] 21-May-2014 17:48:05.865 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.9-dev [junit] 21-May-2014 17:48:05.903 INFO [main] org.apache.coyote.AbstractProtocol.start Starting
Re: buildbot failure in ASF Buildbot on tomcat-trunk
I think I fixed the problem, which was only in the test case. There was a timing issue (the bot seems to be even slower than my 5 years old mac), which provoked an assertion failure. It then provoked the class loading issue because the request was still stuck in the background when the test returned... I hope this will be ok with the next build... Sylvain On 20 mai 2014, at 21:14, Sylvain Laurent wrote: > I'll have a look at this right now. > > > On 19 mai 2014, at 23:28, Konstantin Kolinko wrote: > >> 2014-05-19 23:30 GMT+04:00 : >>> The Buildbot has detected a new failure on builder tomcat-trunk while >>> building ASF Buildbot. >>> Full details are available at: >>> http://ci.apache.org/builders/tomcat-trunk/builds/89 >>> >>> Buildbot URL: http://ci.apache.org/ >>> >>> Buildslave for this Build: bb-vm_ubuntu >>> >>> Build Reason: scheduler >>> Build Source Stamp: [branch tomcat/trunk] 1595898 >>> Blamelist: markt >>> >>> BUILD FAILED: failed compile_1 >>> >> >> The failed test is >> "org.apache.catalina.valves.TestStuckThreadDetectionValve" x NIO. >> >> BIO and NIO2 runs were OK. >> >> http://ci.apache.org/projects/tomcat/tomcat8/1595898/ >> >> http://ci.apache.org/projects/tomcat/tomcat8/1595898/TEST-org.apache.catalina.valves.TestStuckThreadDetectionValve.NIO.txt >> >> >> A difference is that there was an attempt to load a class which failed >> on a stopped web application. >> >> Best regards, >> Konstantin Kolinko >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: dev-h...@tomcat.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
I'll have a look at this right now. On 19 mai 2014, at 23:28, Konstantin Kolinko wrote: > 2014-05-19 23:30 GMT+04:00 : >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/89 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1595898 >> Blamelist: markt >> >> BUILD FAILED: failed compile_1 >> > > The failed test is > "org.apache.catalina.valves.TestStuckThreadDetectionValve" x NIO. > > BIO and NIO2 runs were OK. > > http://ci.apache.org/projects/tomcat/tomcat8/1595898/ > > http://ci.apache.org/projects/tomcat/tomcat8/1595898/TEST-org.apache.catalina.valves.TestStuckThreadDetectionValve.NIO.txt > > > A difference is that there was an attempt to load a class which failed > on a stopped web application. > > Best regards, > Konstantin Kolinko > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2014-05-20 16:29 GMT+04:00 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/92 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1596141 > Blamelist: markt > Logs: http://ci.apache.org/projects/tomcat/tomcat8/1596141/ Failed org.apache.catalina.core.TestAsyncContextImpl. Nothing new here, timing is a bit longer on a slow machine. Failed org.apache.catalina.valves.TestStuckThreadDetectionValve due to class loading. The test run itself was aborted by a signal after running for ~3,5 hours. > process killed by signal 9 > program finished with exit code -1 > elapsedTime=12313.777995 Thus a) BIO, NIO tests were run. It was killed while running NIO2 tests. b) I think it is only control process that was killed. The child junit process is probably still running. (The next buildbot run failed with "Unable to delete directory .../output"). >From my local experience I think the child process will proceed with the rest of the tests. That is unless it is stuck somewhere. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2014-05-19 23:30 GMT+04:00 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/89 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1595898 > Blamelist: markt > > BUILD FAILED: failed compile_1 > The failed test is "org.apache.catalina.valves.TestStuckThreadDetectionValve" x NIO. BIO and NIO2 runs were OK. http://ci.apache.org/projects/tomcat/tomcat8/1595898/ http://ci.apache.org/projects/tomcat/tomcat8/1595898/TEST-org.apache.catalina.valves.TestStuckThreadDetectionValve.NIO.txt A difference is that there was an attempt to load a class which failed on a stopped web application. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2014-03-11 15:21 GMT+01:00 Konstantin Kolinko : > Looking at > org.apache.tomcat.util.net.TestSsl.testRenegotiateWorks(TestSsl.java:206) > more closely, it is a broken test. > +1 on the test being broken as it is now, for me it "works" because I don't get an IOE, but it is null instead. Normally the test returns a meaningful answer (with NIO, it does) so there's something broken. Rémy
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2014-03-11 17:30 GMT+04:00 Konstantin Kolinko :
> 2014-03-11 17:09 GMT+04:00 Rémy Maucherat :
>> 2014-03-11 13:14 GMT+01:00 Konstantin Kolinko :
>>
>>> The only test that fails is org.apache.tomcat.util.net.TestSsl.
>>> Its failure repeats consistently (all 6 of 6 runs), with NIO2.
>>> BIO,NIO,APR connectors do not fail.
>>>
>>> [[[
>>> Testsuite: org.apache.tomcat.util.net.TestSsl
>>> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6,697 sec
>>> -
>>> (...)
>>> -
>>> Testcase: testSimpleSsl took 2,721 sec
>>> Testcase: testKeyPass took 0,499 sec
>>> Testcase: testRenegotiateWorks took 3,418 sec
>>> Caused an ERROR
>>> Connection reset
>>> java.net.SocketException: Connection reset
>>> at java.net.SocketInputStream.read(SocketInputStream.java:196)
>>> at java.net.SocketInputStream.read(SocketInputStream.java:122)
>>> at sun.security.ssl.InputRecord.readFully(InputRecord.java:442)
>>> at sun.security.ssl.InputRecord.read(InputRecord.java:480)
>>> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927)
>>> at
>>> sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884)
>>> at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
>>> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283)
>>> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325)
>>> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177)
>>> at java.io.InputStreamReader.read(InputStreamReader.java:184)
>>> at java.io.BufferedReader.fill(BufferedReader.java:154)
>>> at java.io.BufferedReader.readLine(BufferedReader.java:317)
>>> at java.io.BufferedReader.readLine(BufferedReader.java:382)
>>> at
>>> org.apache.tomcat.util.net.TestSsl.testRenegotiateWorks(TestSsl.java:206)
>>>
>>> That test never failed for me actually. It is a bit suspect that I've had
>> almost no SSL problems overall with the new code, although reusing the NIO
>> secure channel structure probably helped.
>> Can you post the server exception (if any) ?
>>
>
> Which one? Do you mean some code change for that?
>
> In the logs there are no exceptions. The only one is in JUnit output,
> cited above.
>
Looking at
org.apache.tomcat.util.net.TestSsl.testRenegotiateWorks(TestSsl.java:206)
more closely, it is a broken test.
The current code is:
[[[
String line = br.readLine();
while (line != null) {
// For debugging System.out.println(line);
// Linux clients see a Connection Reset in some circumstances and a
// clean close in others.
try {
line = br.readLine();
} catch (IOException ioe) {
line = null;
}
}
]]]
The issue is that it calls br.readLine() twice, but the first call
(before the loop starts) is not wrapped by try/catch.
Best regards,
Konstantin Kolinko
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2014-03-11 14:30 GMT+01:00 Konstantin Kolinko : > >> That test never failed for me actually. It is a bit suspect that I've > had > > almost no SSL problems overall with the new code, although reusing the > NIO > > secure channel structure probably helped. > > Can you post the server exception (if any) ? > > > > Which one? Do you mean some code change for that? > > In the logs there are no exceptions. The only one is in JUnit output, > cited above. > Ok. I meant TestSsl never failed for me. So it looks like there are some timing issues involved. All those tests are a bit "egdy" sometimes, so it's probably not surprising. Should I disable again the tesuite for NIO2 ? Rémy
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2014-03-11 17:09 GMT+04:00 Rémy Maucherat : > 2014-03-11 13:14 GMT+01:00 Konstantin Kolinko : > >> The only test that fails is org.apache.tomcat.util.net.TestSsl. >> Its failure repeats consistently (all 6 of 6 runs), with NIO2. >> BIO,NIO,APR connectors do not fail. >> >> [[[ >> Testsuite: org.apache.tomcat.util.net.TestSsl >> Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6,697 sec >> - >> (...) >> - >> Testcase: testSimpleSsl took 2,721 sec >> Testcase: testKeyPass took 0,499 sec >> Testcase: testRenegotiateWorks took 3,418 sec >> Caused an ERROR >> Connection reset >> java.net.SocketException: Connection reset >> at java.net.SocketInputStream.read(SocketInputStream.java:196) >> at java.net.SocketInputStream.read(SocketInputStream.java:122) >> at sun.security.ssl.InputRecord.readFully(InputRecord.java:442) >> at sun.security.ssl.InputRecord.read(InputRecord.java:480) >> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927) >> at >> sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884) >> at sun.security.ssl.AppInputStream.read(AppInputStream.java:102) >> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283) >> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325) >> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177) >> at java.io.InputStreamReader.read(InputStreamReader.java:184) >> at java.io.BufferedReader.fill(BufferedReader.java:154) >> at java.io.BufferedReader.readLine(BufferedReader.java:317) >> at java.io.BufferedReader.readLine(BufferedReader.java:382) >> at >> org.apache.tomcat.util.net.TestSsl.testRenegotiateWorks(TestSsl.java:206) >> >> That test never failed for me actually. It is a bit suspect that I've had > almost no SSL problems overall with the new code, although reusing the NIO > secure channel structure probably helped. > Can you post the server exception (if any) ? > Which one? Do you mean some code change for that? In the logs there are no exceptions. The only one is in JUnit output, cited above. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2014-03-11 13:14 GMT+01:00 Konstantin Kolinko : > The only test that fails is org.apache.tomcat.util.net.TestSsl. > Its failure repeats consistently (all 6 of 6 runs), with NIO2. > BIO,NIO,APR connectors do not fail. > > [[[ > Testsuite: org.apache.tomcat.util.net.TestSsl > Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6,697 sec > - > (...) > - > Testcase: testSimpleSsl took 2,721 sec > Testcase: testKeyPass took 0,499 sec > Testcase: testRenegotiateWorks took 3,418 sec > Caused an ERROR > Connection reset > java.net.SocketException: Connection reset > at java.net.SocketInputStream.read(SocketInputStream.java:196) > at java.net.SocketInputStream.read(SocketInputStream.java:122) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:442) > at sun.security.ssl.InputRecord.read(InputRecord.java:480) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927) > at > sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884) > at sun.security.ssl.AppInputStream.read(AppInputStream.java:102) > at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283) > at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325) > at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177) > at java.io.InputStreamReader.read(InputStreamReader.java:184) > at java.io.BufferedReader.fill(BufferedReader.java:154) > at java.io.BufferedReader.readLine(BufferedReader.java:317) > at java.io.BufferedReader.readLine(BufferedReader.java:382) > at > org.apache.tomcat.util.net.TestSsl.testRenegotiateWorks(TestSsl.java:206) > > That test never failed for me actually. It is a bit suspect that I've had almost no SSL problems overall with the new code, although reusing the NIO secure channel structure probably helped. Can you post the server exception (if any) ? Rémy
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2014-03-11 15:05 GMT+04:00 Rémy Maucherat : > 2014-03-10 22:16 GMT+01:00 : > >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/5571 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1576014 >> Blamelist: remm >> >> BUILD FAILED: failed compile_1 >> > > There's one failure with NIO2 and TestWebSocketFrameClient. It's working > for me, and seems to be timeout related. Overall, I'm skeptical about > timeout handling in upgrade mode, since it's pretending not to use IO > timeouts, but NIO still has a write timeout (sometimes, depending on the > code that was run before the upgrade). > > This particular test may be taking just a bit too long (the timeout is 5s). > It completes just below 5s when I run it, but takes over 5s on the test > server. Weird ... > Testing trunk @1576281, Win7 JDK 7u51 32-bit The TestWebSocketFrameClient passes for me. No failures in 3 re-runs x 4 connectors. The only test that fails is org.apache.tomcat.util.net.TestSsl. Its failure repeats consistently (all 6 of 6 runs), with NIO2. BIO,NIO,APR connectors do not fail. [[[ Testsuite: org.apache.tomcat.util.net.TestSsl Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6,697 sec - (...) - Testcase: testSimpleSsl took 2,721 sec Testcase: testKeyPass took 0,499 sec Testcase: testRenegotiateWorks took 3,418 sec Caused an ERROR Connection reset java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:196) at java.net.SocketInputStream.read(SocketInputStream.java:122) at sun.security.ssl.InputRecord.readFully(InputRecord.java:442) at sun.security.ssl.InputRecord.read(InputRecord.java:480) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:927) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:884) at sun.security.ssl.AppInputStream.read(AppInputStream.java:102) at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283) at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325) at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177) at java.io.InputStreamReader.read(InputStreamReader.java:184) at java.io.BufferedReader.fill(BufferedReader.java:154) at java.io.BufferedReader.readLine(BufferedReader.java:317) at java.io.BufferedReader.readLine(BufferedReader.java:382) at org.apache.tomcat.util.net.TestSsl.testRenegotiateWorks(TestSsl.java:206) Testcase: testRenegotiateFail took 0,004 sec ]]] Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2014-03-10 22:16 GMT+01:00 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/5571 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1576014 > Blamelist: remm > > BUILD FAILED: failed compile_1 > There's one failure with NIO2 and TestWebSocketFrameClient. It's working for me, and seems to be timeout related. Overall, I'm skeptical about timeout handling in upgrade mode, since it's pretending not to use IO timeouts, but NIO still has a write timeout (sometimes, depending on the code that was run before the upgrade). This particular test may be taking just a bit too long (the timeout is 5s). It completes just below 5s when I run it, but takes over 5s on the test server. Weird ... Rémy
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2014-03-06 2:46 GMT+04:00 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/5558 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1574657 > Blamelist: markt > > BUILD FAILED: failed compile_1 > It is indeed a failing test: [junit] Test org.apache.jasper.servlet.TestJspCServletContext FAILED for both BIO and NIO [[[ Testcase: testWebresources took 0.076 sec Caused an ERROR null java.lang.NullPointerException at org.apache.jasper.servlet.JspCServletContext.getEffectiveMajorVersion(JspCServletContext.java:677) at org.apache.jasper.servlet.TestJspCServletContext.testWebresources(TestJspCServletContext.java:121) ]]] It is the same NPE error for all test cases. http://ci.apache.org/projects/tomcat/tomcat8/logs/1574657/TEST-org.apache.jasper.servlet.TestJspCServletContext.BIO.txt Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 25/11/2013 16:11, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/5264 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1545288 > Blamelist: markt > > BUILD FAILED: failed compile_1 This is a result of the deployXML changes. I'm in the middle of fixing it. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 05/11/2013 11:40, Konstantin Kolinko wrote: > 2013/11/5 : >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/5174 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1538924 >> Blamelist: markt >> >> BUILD FAILED: failed compile_1 >> > > > It is the first run after resource refactorings in trunk (r1538805 - > r1538839). It was the refactoring of the JAR abstraction used by Jasper that triggered those failures. I've fixed at least some and hopefully all of those now. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2013/11/5 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/5174 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1538924 > Blamelist: markt > > BUILD FAILED: failed compile_1 > It is the first run after resource refactorings in trunk (r1538805 - r1538839). There such errors in stdio log: [junit] Caused by: java.lang.ClassCastException: sun.net.www.protocol.file.FileURLConnection cannot be cast to java.net.JarURLConnection [junit] at org.apache.tomcat.util.scan.UrlJar.createJarInputStream(UrlJar.java:115) [junit] at org.apache.tomcat.util.scan.UrlJar.(UrlJar.java:38) [junit] at org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:41) [junit] at org.apache.jasper.compiler.TldLocation.(TldLocation.java:37) [junit] at org.apache.jasper.compiler.TldLocationsCache.(TldLocationsCache.java:80) [junit] at org.apache.jasper.servlet.JasperInitializer.onStartup(JasperInitializer.java:69) [junit] at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5232) [junit] at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) [junit] ... 7 more which prevents Tomcat in the tests from starting. There are no new files at http://ci.apache.org/projects/tomcat/tomcat8/ Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2013/8/3 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/4783 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1509866 > Blamelist: rjung > > BUILD FAILED: failed compile_1 > BIO x TestWsWebSocketContainer Testcase: testSmallTextBufferServerTextMessage took 0.105 sec Caused an ERROR The WebSocket session has been closed and no method (apart from close()) may be called on a closed session java.lang.IllegalStateException: The WebSocket session has been closed and no method (apart from close()) may be called on a closed session at org.apache.tomcat.websocket.WsSession.checkState(WsSession.java:607) at org.apache.tomcat.websocket.WsSession.getUserProperties(WsSession.java:556) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.getBlockingSendTimeout(WsRemoteEndpointImplBase.java:360) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPartialString(WsRemoteEndpointImplBase.java:195) at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendString(WsRemoteEndpointImplBase.java:155) at org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:37) at org.apache.tomcat.websocket.TestWsWebSocketContainer.doBufferTest(TestWsWebSocketContainer.java:256) at org.apache.tomcat.websocket.TestWsWebSocketContainer.testSmallTextBufferServerTextMessage(TestWsWebSocketContainer.java:167) http://ci.apache.org/projects/tomcat/tomcat8/logs/1509866/TEST-org.apache.tomcat.websocket.TestWsWebSocketContainer.BIO.txt Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 21/07/2013 10:34, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/4727 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1505310 > Blamelist: markt > > BUILD FAILED: failed compile_1 This is because I accidentally committed some tests for the EL that current fail that shouldn't. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 15/07/2013 17:06, Konstantin Kolinko wrote: > 2013/7/15 : >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/4685 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1503169 >> Blamelist: markt >> >> BUILD FAILED: failed compile_1 >> > > > org.apache.el.parser.TestAstLambdaExpression > fails with StackOverflowError, > > http://ci.apache.org/projects/tomcat/tomcat8/logs/1503253/TEST-org.apache.el.parser.TestAstLambdaExpression.BIO.txt Whoops. Fixed. Thanks. Looking at why the CI build was failing was on my TODO list. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2013/7/15 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/4685 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1503169 > Blamelist: markt > > BUILD FAILED: failed compile_1 > org.apache.el.parser.TestAstLambdaExpression fails with StackOverflowError, http://ci.apache.org/projects/tomcat/tomcat8/logs/1503253/TEST-org.apache.el.parser.TestAstLambdaExpression.BIO.txt Testcase: testSpec03 took 0.007 sec Caused an ERROR null java.lang.StackOverflowError at org.apache.el.parser.AstLambdaExpression.invoke(AstLambdaExpression.java:68) at org.apache.el.parser.AstLambdaExpression.getValue(AstLambdaExpression.java:45) at org.apache.el.parser.AstLambdaExpression.invoke(AstLambdaExpression.java:68) at org.apache.el.parser.AstLambdaExpression.getValue(AstLambdaExpression.java:45) Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
Konstantin Kolinko wrote: >The only failing test is >"org.apache.tomcat.websocket.TestWebSocketFrameClient" It worked when I tested it :) My guess is it just needs longer to complete. I'll increase the wait time to 60s when I get back to my desk. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2013/7/11 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/4650 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1502181 > Blamelist: kkolinko,markt > > BUILD FAILED: failed compile_1 > The only failing test is "org.apache.tomcat.websocket.TestWebSocketFrameClient" With BIO: [[[ Testcase: testConnectToServerEndpointSSL took 13.539 sec FAILED expected:<10> but was:<44898> junit.framework.AssertionFailedError: expected:<10> but was:<44898> at org.apache.tomcat.websocket.TestWebSocketFrameClient.testConnectToServerEndpointSSL(TestWebSocketFrameClient.java:82) ]]] With NIO: [[[ Testcase: testConnectToServerEndpointSSL took 13.631 sec FAILED expected:<10> but was:<45741> junit.framework.AssertionFailedError: expected:<10> but was:<45741> at org.apache.tomcat.websocket.TestWebSocketFrameClient.testConnectToServerEndpointSSL(TestWebSocketFrameClient.java:82) ]]] Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 09/07/2013 06:39, Violeta Georgieva wrote: > 2013/7/9 Konstantin Kolinko wrote: >> >> 2013/7/9 : >>> The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. >>> Full details are available at: >>> http://ci.apache.org/builders/tomcat-trunk/builds/4625 >>> >>> Buildbot URL: http://ci.apache.org/ >>> >>> Buildslave for this Build: bb-vm_ubuntu >>> >>> Build Reason: scheduler >>> Build Source Stamp: [branch tomcat/trunk] 1500979 >>> Blamelist: markt >>> >>> BUILD FAILED: failed compile_1 >>> >> >> >> Test org.apache.catalina.core.TestApplicationContext FAILED >> Test org.apache.catalina.core.TestStandardContext FAILED >> and many others are failing..., >> > > The build is OK now. Thanks for those fixes. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2013/7/9 Konstantin Kolinko wrote: > > 2013/7/9 : > > The Buildbot has detected a new failure on builder tomcat-trunk while building ASF Buildbot. > > Full details are available at: > > http://ci.apache.org/builders/tomcat-trunk/builds/4625 > > > > Buildbot URL: http://ci.apache.org/ > > > > Buildslave for this Build: bb-vm_ubuntu > > > > Build Reason: scheduler > > Build Source Stamp: [branch tomcat/trunk] 1500979 > > Blamelist: markt > > > > BUILD FAILED: failed compile_1 > > > > > Test org.apache.catalina.core.TestApplicationContext FAILED > Test org.apache.catalina.core.TestStandardContext FAILED > and many others are failing..., > The build is OK now. Thanks Violeta
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2013/7/9 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/4625 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1500979 > Blamelist: markt > > BUILD FAILED: failed compile_1 > Test org.apache.catalina.core.TestApplicationContext FAILED Test org.apache.catalina.core.TestStandardContext FAILED and many others are failing..., http://ci.apache.org/projects/tomcat/tomcat8/logs/1500979/TEST-org.apache.catalina.core.TestStandardContext.BIO.txt java.lang.ClassNotFoundException: org.apache.catalina.deploy.FilterDef at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1466) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1311) at org.apache.tomcat.util.digester.ObjectCreateRule.begin(ObjectCreateRule.java:116) at org.apache.tomcat.util.digester.Digester.startElement(Digester.java:1171) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:506) at (...) at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1432) at org.apache.catalina.startup.ContextConfig.parseWebXml(ContextConfig.java:2001) Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 08/07/2013 12:21, Konstantin Kolinko wrote: > Apparently there is a resolver in Jasper > (org.apache.jasper.xmlparser.MyEntityResolver) and it is now stuck as > the files have been moved. Thanks. Fixed. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
013/7/8 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/4614 > > Buildbot URL: http://ci.apache.org/ > Test javax.el.TestCompositeELResolver FAILED Test org.apache.jasper.compiler.TestValidator FAILED Test org.apache.jasper.tagplugins.jstl.core.TestForEach FAILED Test org.apache.jasper.tagplugins.jstl.core.TestOut FAILED Test org.apache.jasper.tagplugins.jstl.core.TestSet FAILED both for BIO & NIO. Looking at http://ci.apache.org/projects/tomcat/tomcat8/logs/1500632/TEST-javax.el.TestCompositeELResolver.BIO.txt WARNING: Failed to scan JAR [file:/home/buildslave3/slave3/tomcat-trunk/build/webapps/examples/WEB-INF/lib/standard.jar] from /WEB-INF/lib java.io.IOException: org.apache.jasper.JasperException: XML parsing error on file file:/home/buildslave3/slave3/tomcat-trunk/build/webapps/examples/WEB-INF/lib/standard.jar at org.apache.jasper.compiler.TldLocationsCache.tldScanStream(TldLocationsCache.java:480) (...) Caused by: org.xml.sax.SAXException: Internal Error: File /javax/servlet/jsp/resources/web-jsptaglibrary_1_2.dtd not found at org.apache.jasper.xmlparser.MyEntityResolver.resolveEntity(ParserUtils.java:216) at (...) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:300) at org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:96) Apparently there is a resolver in Jasper (org.apache.jasper.xmlparser.MyEntityResolver) and it is now stuck as the files have been moved. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2013/2/12 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/3907 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1445125 > Blamelist: kkolinko > > BUILD FAILED: failed compile_1 > http://ci.apache.org/projects/tomcat/tomcat8/logs/1445125/TEST-org.apache.tomcat.websocket.TestWsWebSocketContainer.BIO.txt [[[ Testcase: testTimeoutClientContainer took 5.178 sec FAILED Time out was [4999] ms junit.framework.AssertionFailedError: Time out was [4999] ms at org.apache.tomcat.websocket.TestWsWebSocketContainer.doTestTimeoutClient(TestWsWebSocketContainer.java:317) at org.apache.tomcat.websocket.TestWsWebSocketContainer.testTimeoutClientContainer(TestWsWebSocketContainer.java:260) ]]] Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2012/12/5 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/3637 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1417224 > Blamelist: kkolinko,markt > > BUILD FAILED: failed compile_1 > TEST-org.apache.catalina.core.TestAsyncContextImpl.NIO.txt Testcase: testAsyncStartNoComplete took 5.277 sec FAILED Uri: /, Status: 500, Time: 853 junit.framework.AssertionFailedError: Uri: /, Status: 500, Time: 853 at org.apache.catalina.valves.TesterAccessLogValve.validateAccessLog(TesterAccessLogValve.java:81) at org.apache.catalina.core.TestAsyncContextImpl.testAsyncStartNoComplete(TestAsyncContextImpl.java:181) It was expected to complete no sooner than in 1000 ms (with error margin of 100). The actual value in the access log was 853. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2012/11/25 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/3597 > Test org.apache.tomcat.util.scan.TestJarScanner FAILED (BIO + NIO) Testcase: testJarsToSkipFormat took 0.274 sec FAILED Token "websocket-api.jarcommons-beanutils*.jar" contains sub string ".jar" or separator "," is missing expected:<35> but was:<13> junit.framework.AssertionFailedError: Token "websocket-api.jarcommons-beanutils*.jar" contains sub string ".jar" or separator "," is missing expected:<35> but was:<13> at org.apache.tomcat.util.scan.TestJarScanner.testJarsToSkipFormat(TestJarScanner.java:45) It is good that we have such a test. It should be easy to fix. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 13/11/2012 11:31, Mark Thomas wrote: > On 12/11/2012 05:25, Konstantin Kolinko wrote: >> 2012/11/12 : >>> The Buildbot has detected a new failure on builder tomcat-trunk while >>> building ASF Buildbot. >>> Full details are available at: >>> http://ci.apache.org/builders/tomcat-trunk/builds/3550 >>> >>> Buildbot URL: http://ci.apache.org/ >>> >>> Buildslave for this Build: bb-vm_ubuntu >>> >>> Build Reason: scheduler >>> Build Source Stamp: [branch tomcat/trunk] 1408165 >>> Blamelist: markt >>> >>> BUILD FAILED: failed compile_1 >>> >> >> http://ci.apache.org/projects/tomcat/tomcat8/logs/1408165/TEST-org.apache.catalina.core.TestAsyncContextImpl.NIO.txt >> >> Testsuite: org.apache.catalina.core.TestAsyncContextImpl >> Tests run: 41, Failures: 1, Errors: 0, Time elapsed: 79.256 sec >> >> Testcase: testTimeoutListenerCompleteNoDispatch took 5.125 sec >> FAILED >> Uri: /async, Status: 200, Time: 2921 >> junit.framework.AssertionFailedError: Uri: /async, Status: 200, Time: 2921 >> at >> org.apache.catalina.valves.TesterAccessLogValve.validateAccessLog(TesterAccessLogValve.java:81) >> at >> org.apache.catalina.core.TestAsyncContextImpl.doTestTimeout(TestAsyncContextImpl.java:499) >> at >> org.apache.catalina.core.TestAsyncContextImpl.testTimeoutListenerCompleteNoDispatch(TestAsyncContextImpl.java:387) >> >> >> The code is >> alvGlobal.validateAccessLog(1, 200, TimeoutServlet.ASYNC_TIMEOUT, >> TimeoutServlet.ASYNC_TIMEOUT + TIMEOUT_MARGIN + >> REQUEST_TIME); >> >> TimeoutServlet.ASYNC_TIMEOUT is 3000, so it executed faster (2921) >> than expected. > > That is close enough that I wonder if we have a clock resolution issue > here. The other possibility is differences in when the various timers > are started. A short GC pause in the wrong place might be able to > trigger this. I'll dig a little deeper. Looks like it could be either. I'll up the error margin from 10ms to 100ms. That should fix most false failures without introducing any false passes. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 12/11/2012 05:25, Konstantin Kolinko wrote: > 2012/11/12 : >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/3550 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1408165 >> Blamelist: markt >> >> BUILD FAILED: failed compile_1 >> > > http://ci.apache.org/projects/tomcat/tomcat8/logs/1408165/TEST-org.apache.catalina.core.TestAsyncContextImpl.NIO.txt > > Testsuite: org.apache.catalina.core.TestAsyncContextImpl > Tests run: 41, Failures: 1, Errors: 0, Time elapsed: 79.256 sec > > Testcase: testTimeoutListenerCompleteNoDispatch took 5.125 sec > FAILED > Uri: /async, Status: 200, Time: 2921 > junit.framework.AssertionFailedError: Uri: /async, Status: 200, Time: 2921 > at > org.apache.catalina.valves.TesterAccessLogValve.validateAccessLog(TesterAccessLogValve.java:81) > at > org.apache.catalina.core.TestAsyncContextImpl.doTestTimeout(TestAsyncContextImpl.java:499) > at > org.apache.catalina.core.TestAsyncContextImpl.testTimeoutListenerCompleteNoDispatch(TestAsyncContextImpl.java:387) > > > The code is > alvGlobal.validateAccessLog(1, 200, TimeoutServlet.ASYNC_TIMEOUT, > TimeoutServlet.ASYNC_TIMEOUT + TIMEOUT_MARGIN + > REQUEST_TIME); > > TimeoutServlet.ASYNC_TIMEOUT is 3000, so it executed faster (2921) > than expected. That is close enough that I wonder if we have a clock resolution issue here. The other possibility is differences in when the various timers are started. A short GC pause in the wrong place might be able to trigger this. I'll dig a little deeper. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2012/11/12 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/3550 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1408165 > Blamelist: markt > > BUILD FAILED: failed compile_1 > http://ci.apache.org/projects/tomcat/tomcat8/logs/1408165/TEST-org.apache.catalina.core.TestAsyncContextImpl.NIO.txt Testsuite: org.apache.catalina.core.TestAsyncContextImpl Tests run: 41, Failures: 1, Errors: 0, Time elapsed: 79.256 sec Testcase: testTimeoutListenerCompleteNoDispatch took 5.125 sec FAILED Uri: /async, Status: 200, Time: 2921 junit.framework.AssertionFailedError: Uri: /async, Status: 200, Time: 2921 at org.apache.catalina.valves.TesterAccessLogValve.validateAccessLog(TesterAccessLogValve.java:81) at org.apache.catalina.core.TestAsyncContextImpl.doTestTimeout(TestAsyncContextImpl.java:499) at org.apache.catalina.core.TestAsyncContextImpl.testTimeoutListenerCompleteNoDispatch(TestAsyncContextImpl.java:387) The code is alvGlobal.validateAccessLog(1, 200, TimeoutServlet.ASYNC_TIMEOUT, TimeoutServlet.ASYNC_TIMEOUT + TIMEOUT_MARGIN + REQUEST_TIME); TimeoutServlet.ASYNC_TIMEOUT is 3000, so it executed faster (2921) than expected. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2012/11/3 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/3521 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1405353 > Blamelist: markt > > BUILD FAILED: failed compile_1 > Two subsequent builds have also failed. 3523: http://ci.apache.org/builders/tomcat-trunk/builds/3523/steps/compile_1/logs/stdio [junit] INFO: Destroying ProtocolHandler ["http-bio-127.0.0.1-auto-6-35611"] [junit] Test org.apache.catalina.authenticator.TestSSOnonLoginAndDigestAuthenticator FAILED [junit] INFO: Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-6-49733"] [junit] Test org.apache.catalina.authenticator.TestSSOnonLoginAndDigestAuthenticator FAILED The failure in Tomcat 7 testsuite is due to the same test, both BIO and NIO. http://ci.apache.org/projects/tomcat/tomcat8/logs/1405364/TEST-org.apache.catalina.authenticator.TestSSOnonLoginAndDigestAuthenticator.NIO.txt Testsuite: org.apache.catalina.authenticator.TestSSOnonLoginAndDigestAuthenticator Tests run: 6, Failures: 4, Errors: 0, Time elapsed: 3.05 sec All 4 failures are printing expected:<200> but was:<401> Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 24/10/2012 09:35, Mark Thomas wrote: > On 24/10/2012 00:13, build...@apache.org wrote: >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/3484 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1401503 >> Blamelist: markt >> >> BUILD FAILED: failed compile_1 > > This worked locally on Windows before I did the commit but I didn't test > on Linux. I also see failures locally on Linux. I suspect a \ vs / issue > but I'll dig into this now. Nope. I got that bit right :). The issue is an older svn client that leaves .svn directories all over the place which then breaks the test. Looking at options now... Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 24/10/2012 00:13, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/3484 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1401503 > Blamelist: markt > > BUILD FAILED: failed compile_1 This worked locally on Windows before I did the commit but I didn't test on Linux. I also see failures locally on Linux. I suspect a \ vs / issue but I'll dig into this now. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 03/07/2012 21:35, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/3156 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1356898 > Blamelist: fhanik > > BUILD FAILED: failed compile_1 Timing error. We have been seeing a few of these lately. May be GC related? Anyway, nothing that obviously needs fixing at this point. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: buildbot failure in ASF Buildbot on tomcat-trunk
Will fix! > -Original Message- > From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] > Sent: Tuesday, July 03, 2012 12:51 PM > To: Tomcat Developers List > Subject: Re: buildbot failure in ASF Buildbot on tomcat-trunk > > 2012/7/3 : > > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > > Full details are available at: > > http://ci.apache.org/builders/tomcat-trunk/builds/3153 > > > > NPE in TestStandardWrapper, both NIO and BIO: > [[[ > Testcase: testSecurityAnnotationsMethods2 took 0.106 sec > Caused an ERROR > null > java.lang.NullPointerException > at > org.apache.catalina.startup.TomcatBaseTest$1.available(TomcatBaseTest.ja > va:308) > at > org.apache.catalina.startup.TomcatBaseTest.postUrl(TomcatBaseTest.java:3 > 51) > at > org.apache.catalina.startup.TomcatBaseTest.postUrl(TomcatBaseTest.java:3 > 11) > at > org.apache.catalina.core.TestStandardWrapper.doTest(TestStandardWrapper. > java:263) > at > org.apache.catalina.core.TestStandardWrapper.testSecurityAnnotationsMeth > ods2(TestStandardWrapper.java:85) > ]]] > > See logs here: > http://ci.apache.org/projects/tomcat/tomcat8/logs/ > ->1356852/ > > Best regards, > Konstantin Kolinko > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2012/7/3 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/3153 > NPE in TestStandardWrapper, both NIO and BIO: [[[ Testcase: testSecurityAnnotationsMethods2 took 0.106 sec Caused an ERROR null java.lang.NullPointerException at org.apache.catalina.startup.TomcatBaseTest$1.available(TomcatBaseTest.java:308) at org.apache.catalina.startup.TomcatBaseTest.postUrl(TomcatBaseTest.java:351) at org.apache.catalina.startup.TomcatBaseTest.postUrl(TomcatBaseTest.java:311) at org.apache.catalina.core.TestStandardWrapper.doTest(TestStandardWrapper.java:263) at org.apache.catalina.core.TestStandardWrapper.testSecurityAnnotationsMethods2(TestStandardWrapper.java:85) ]]] See logs here: http://ci.apache.org/projects/tomcat/tomcat8/logs/ ->1356852/ Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 27/06/2012 05:48, Konstantin Kolinko wrote: > 2012/6/27 : >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/3129 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1354255 >> Blamelist: markt >> >> BUILD FAILED: failed compile_1 >> > > > TestNamingContext failed for BIO and NIO. > Test logs: > http://ci.apache.org/projects/tomcat/tomcat8/logs/1354255/ > > Testcase: testBug53465 took 0.89 sec > FAILED > expected:<200> but was:<404> > > It is the recently added test. Hmm. I wonder if I forgot to svn add the new JSP this test uses... Yep. Fixing now... Sorry for the noise. > BTW, the NIO log shows a lot of NullPointerExceptions. Those happen > after ProtocolHandler is stopped and destroyed. I'll take a look at those too unless someone beats me to it. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2012/6/27 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/3129 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1354255 > Blamelist: markt > > BUILD FAILED: failed compile_1 > TestNamingContext failed for BIO and NIO. Test logs: http://ci.apache.org/projects/tomcat/tomcat8/logs/1354255/ Testcase: testBug53465 took 0.89 sec FAILED expected:<200> but was:<404> It is the recently added test. BTW, the NIO log shows a lot of NullPointerExceptions. Those happen after ProtocolHandler is stopped and destroyed. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 06/06/2012 00:58, Mark Thomas wrote: > On 05/06/2012 22:37, build...@apache.org wrote: >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/3039 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1346581 >> Blamelist: markt > > I now have access to the host where this build runs and can repeat the > failure easily. I intend to investigate further over the next few days > with a view to identifying the root cause and hopefully fixing it. I think I have found the problem and fixed it. The short version was that we weren't handling close properly if a connection wasn't registered for read or write at the time the close is processed. This is unlikely but seems to happen consistently on the CI server. Final proof will be the CI results for the next few commits. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 05/06/2012 22:37, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/3039 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1346581 > Blamelist: markt I now have access to the host where this build runs and can repeat the failure easily. I intend to investigate further over the next few days with a view to identifying the root cause and hopefully fixing it. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
28.03.2012 19:42, Konstantin Kolinko: > 2012/3/28 Markus Schönhaber : >> 28.03.2012 18:31, Filip Hanik (mailing lists): >> >>> Is it my email client, or are some of these emails empty? >> >> It's probably your client. That's the body of the mail you responded to: [...] > Viewing the source of the message, it is encoded in base64. > > What is a bit strange it is that the base64 chars come in two blocks > of different width, and there is "=" at the end of the last line of > first block. I doubt that the equals sign is allowed in the middle of > data. You're right, I didn't notice this. Seems like the list software simply glues the base64-encoded footer to the existing message. I took a (just superficial) look at RFC 4648 and didn't see that this is explicitly forbidden but from this http://tools.ietf.org/html/rfc4648#section-3.1 | 3.1. Line Feeds in Encoded Data | |MIME [4] is often used as a reference for base 64 encoding. However, |MIME does not define "base 64" per se, but rather a "base 64 Content- |Transfer-Encoding" for use within MIME. As such, MIME enforces a |limit on line length of base 64-encoded data to 76 characters. MIME |inherits the encoding from Privacy Enhanced Mail (PEM) [3], stating |that it is "virtually identical"; however, PEM uses a line length of |64 characters. The MIME and PEM limits are both due to limits within |SMTP. | |Implementations MUST NOT add line feeds to base-encoded data unless |the specification referring to this document explicitly directs base |encoders to add line feeds after a specific number of characters. it might - IMO - be deduced that the particular input we have here, is not a valid base64-encoded string (the line-length of 72 chars in the footer block seems suspicious too). BTW: If one feeds the complete body of the mail to python's base64.b64decode the footer will be missing while thunderbird decodes that as well. Bottom line: Regardless whether or not it really is violating the spec to glue two base64-encoded strings together and expect the result to be a new, valid, base64-encoded string - in practice, at least, it seems to be a bad idea. -- Regards mks - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2012/3/28 Markus Schönhaber : > 28.03.2012 18:31, Filip Hanik (mailing lists): > >> Is it my email client, or are some of these emails empty? > > It's probably your client. That's the body of the mail you responded to: > >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/2901 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1306410 >> Blamelist: fhanik >> >> BUILD FAILED: failed compile_1 >> >> sincerely, >> -The Buildbot >> Viewing the source of the message, it is encoded in base64. What is a bit strange it is that the base64 chars come in two blocks of different width, and there is "=" at the end of the last line of first block. I doubt that the equals sign is allowed in the middle of data. To see the bytes, look at [2] for a link to "View raw message" Decoding the second block gives: [[[ - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org ]]] GMail loses this second block on some (not all) messages, so it does not display it to me. Looking at mailing list archives, markmail [1] shows the footer, ASF mail archive [2] looses it. In [2] -> click "View raw message" -> the same base64 bytes as in my copy of this message in GMail. [1] http://markmail.org/message/uimbvh5sf33it65l [2] http://mail-archives.apache.org/mod_mbox/tomcat-dev/201203.mbox/%3C20120328160023.225BFC00A0%40aegis.apache.org%3E Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
28.03.2012 18:31, Filip Hanik (mailing lists): > Is it my email client, or are some of these emails empty? It's probably your client. That's the body of the mail you responded to: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2901 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1306410 > Blamelist: fhanik > > BUILD FAILED: failed compile_1 > > sincerely, > -The Buildbot > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: buildbot failure in ASF Buildbot on tomcat-trunk
Is it my email client, or are some of these emails empty? > -Original Message- > From: build...@apache.org [mailto:build...@apache.org] > Sent: Wednesday, March 28, 2012 10:00 AM > To: dev@tomcat.apache.org > Subject: buildbot failure in ASF Buildbot on tomcat-trunk > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 21/03/2012 20:10, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2877 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1303521 > Blamelist: markt > > BUILD FAILED: failed compile_1 I think I have figured out what is going on here. When the tomcat-7-trunk and tomcat-trunk builds run at the same time, the cluster tests can get confused as rather than two separate clusters, we get one big cluster. Depending on what the test checks, this may cause a failure. We need to look at ways to keep the clusters separate and/or stop the tests running at the same time. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2012/3/7 Konstantin Kolinko : > 2012/3/7 Mark Thomas : >> On 06/03/2012 21:27, build...@apache.org wrote: >>> The Buildbot has detected a new failure on builder tomcat-trunk while >>> building ASF Buildbot. >>> Full details are available at: >>> http://ci.apache.org/builders/tomcat-trunk/builds/2816 >>> >>> Buildbot URL: http://ci.apache.org/ >>> >>> Buildslave for this Build: bb-vm_ubuntu >>> >>> Build Reason: scheduler >>> Build Source Stamp: [branch tomcat/trunk] 1297717 >>> Blamelist: markt >>> >>> BUILD FAILED: failed compile_1 >> >> Drat. The Comet unit tests are still failing. I had hoped we had fixed that. >> >> We really need the Gump run to fail so we have access to the full logs >> to better understand which test is failing and why. Either that or a way >> to extract the logs from buildbot. Hmm. I probably have access to that >> machine. I'll go and have a look. >> > > One more: > Gump MacOS server fails the Comet tests in trunk and 7.0.x > > See > http://tomcat.apache.org/ci.html#Gump > then look for "Adam" > > http://adam.apache.org/gump/tomcat-trunk/tomcat-trunk-test/gump_file/TEST-org.apache.catalina.comet.TestCometProcessor.NIO.txt.html > > The trunk and tc7.0.x runs have the same failure - the stop test fails: > [[[ > Testcase: testCometConnectorStop took 13.144 sec > FAILED > Comet END event not received > junit.framework.AssertionFailedError: Comet END event not received > at > org.apache.catalina.comet.TestCometProcessor.testCometConnectorStop(TestCometProcessor.java:325) > ]]] > > Log: > > [[[ > Mar 6, 2012 11:43:24 AM org.apache.coyote.AbstractProtocol init > INFO: Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-6"] > Mar 6, 2012 11:43:24 AM org.apache.tomcat.util.net.NioSelectorPool > getSharedSelector > INFO: Using a shared selector for servlet write/read > Mar 6, 2012 11:43:24 AM org.apache.catalina.core.StandardService startInternal > INFO: Starting service Tomcat > Mar 6, 2012 11:43:24 AM org.apache.catalina.core.StandardEngine startInternal > INFO: Starting Servlet Engine: Apache Tomcat/8.0.0-dev > Mar 6, 2012 11:43:24 AM org.apache.coyote.AbstractProtocol start > INFO: Starting ProtocolHandler ["http-nio-127.0.0.1-auto-6"] > Mar 6, 2012 11:43:27 AM org.apache.coyote.AbstractProtocol stop > INFO: Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-6"] > Mar 6, 2012 11:43:37 AM org.apache.coyote.AbstractProtocol destroy > INFO: Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-6"] > Mar 6, 2012 11:43:37 AM org.apache.catalina.comet.TestCometProcessor > testCometConnectorStop > SEVERE: Status: > WriterThread exception: null > ReaderThread exception: java.net.SocketTimeoutException: Read timed out > Last message: [Client: READ: 4 bytes] > Last response line: [Client: READ: 4 bytes] > Last comet event: [READ] > Mar 6, 2012 11:43:37 AM org.apache.catalina.core.StandardService stopInternal > INFO: Stopping service Tomcat > ]]] > > It is likely that Tomcat stops without delivering END event to the > servlet. So the last event that it sees was "READ". > > I think that this issue is not a serious one. > And that is the same as in Buildbot stdout log from http://ci.apache.org/builders/tomcat-trunk/builds/2816/ [[[ [junit] SEVERE: Status: [junit] WriterThread exception: null [junit] ReaderThread exception: java.net.SocketTimeoutException: Read timed out [junit] Last message: [Client: READ: 4 bytes] [junit] Last response line: [Client: READ: 4 bytes] [junit] Last comet event: [READ] [junit] Mar 6, 2012 9:18:31 PM org.apache.catalina.core.StandardService stopInternal [junit] INFO: Stopping service Tomcat [junit] Test org.apache.catalina.comet.TestCometProcessor FAILED ]]] Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2012/3/7 Mark Thomas : > On 06/03/2012 21:27, build...@apache.org wrote: >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/2816 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1297717 >> Blamelist: markt >> >> BUILD FAILED: failed compile_1 > > Drat. The Comet unit tests are still failing. I had hoped we had fixed that. > > We really need the Gump run to fail so we have access to the full logs > to better understand which test is failing and why. Either that or a way > to extract the logs from buildbot. Hmm. I probably have access to that > machine. I'll go and have a look. > One more: Gump MacOS server fails the Comet tests in trunk and 7.0.x See http://tomcat.apache.org/ci.html#Gump then look for "Adam" http://adam.apache.org/gump/tomcat-trunk/tomcat-trunk-test/gump_file/TEST-org.apache.catalina.comet.TestCometProcessor.NIO.txt.html The trunk and tc7.0.x runs have the same failure - the stop test fails: [[[ Testcase: testCometConnectorStop took 13.144 sec FAILED Comet END event not received junit.framework.AssertionFailedError: Comet END event not received at org.apache.catalina.comet.TestCometProcessor.testCometConnectorStop(TestCometProcessor.java:325) ]]] Log: [[[ Mar 6, 2012 11:43:24 AM org.apache.coyote.AbstractProtocol init INFO: Initializing ProtocolHandler ["http-nio-127.0.0.1-auto-6"] Mar 6, 2012 11:43:24 AM org.apache.tomcat.util.net.NioSelectorPool getSharedSelector INFO: Using a shared selector for servlet write/read Mar 6, 2012 11:43:24 AM org.apache.catalina.core.StandardService startInternal INFO: Starting service Tomcat Mar 6, 2012 11:43:24 AM org.apache.catalina.core.StandardEngine startInternal INFO: Starting Servlet Engine: Apache Tomcat/8.0.0-dev Mar 6, 2012 11:43:24 AM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-nio-127.0.0.1-auto-6"] Mar 6, 2012 11:43:27 AM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler ["http-nio-127.0.0.1-auto-6"] Mar 6, 2012 11:43:37 AM org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-6"] Mar 6, 2012 11:43:37 AM org.apache.catalina.comet.TestCometProcessor testCometConnectorStop SEVERE: Status: WriterThread exception: null ReaderThread exception: java.net.SocketTimeoutException: Read timed out Last message: [Client: READ: 4 bytes] Last response line: [Client: READ: 4 bytes] Last comet event: [READ] Mar 6, 2012 11:43:37 AM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Tomcat ]]] It is likely that Tomcat stops without delivering END event to the servlet. So the last event that it sees was "READ". I think that this issue is not a serious one. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2012/3/7 Mark Thomas : > On 06/03/2012 21:27, build...@apache.org wrote: >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/2816 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1297717 >> Blamelist: markt >> >> BUILD FAILED: failed compile_1 > > Drat. The Comet unit tests are still failing. I had hoped we had fixed that. > > We really need the Gump run to fail so we have access to the full logs > to better understand which test is failing and why. Either that or a way > to extract the logs from buildbot. Hmm. I probably have access to that > machine. I'll go and have a look. > It is possible to make junit to spew the logs onto stdout by defining junit.formatter.usefile=false I mentioned that in https://issues.apache.org/jira/browse/INFRA-3948 Maybe go this way, because the task of providing us access to separate log files like in Gump has no progress at all. >From RAT report I know that buildbot has build.properties file in the root of the project. I do not know how it is created - probably by some shell script. The new property can be added there. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 06/03/2012 21:27, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2816 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1297717 > Blamelist: markt > > BUILD FAILED: failed compile_1 Drat. The Comet unit tests are still failing. I had hoped we had fixed that. We really need the Gump run to fail so we have access to the full logs to better understand which test is failing and why. Either that or a way to extract the logs from buildbot. Hmm. I probably have access to that machine. I'll go and have a look. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 02/03/2012 00:13, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2802 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1295998 > Blamelist: fhanik > > BUILD FAILED: failed compile_1 Odd. That is an async failure. Maybe timing related. I don't believe we have access to the logs to see which test failed on buildbot. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 02/02/2012 18:10, Konstantin Kolinko wrote: > Nearly all tests at both Gump and Buildbot are currently failing with > > null > java.lang.NullPointerException > at java.io.File.(File.java:239) > at org.apache.catalina.startup.Tomcat.initBaseDir(Tomcat.java:609) > at org.apache.catalina.startup.Tomcat.getServer(Tomcat.java:466) > at org.apache.catalina.startup.Tomcat.getService(Tomcat.java:412) > at > org.apache.catalina.startup.TomcatBaseTest.setUp(TomcatBaseTest.java:108) That'll be me. Sorry. Trying to do too much in parallel. Mark > > > Best regards, > Konstantin Kolinko > > 2012/2/2 : >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/2700 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1239531 >> Blamelist: markt >> >> BUILD FAILED: failed compile_1 >> >> sincerely, >> -The Buildbot >> >> >> > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
Nearly all tests at both Gump and Buildbot are currently failing with null java.lang.NullPointerException at java.io.File.(File.java:239) at org.apache.catalina.startup.Tomcat.initBaseDir(Tomcat.java:609) at org.apache.catalina.startup.Tomcat.getServer(Tomcat.java:466) at org.apache.catalina.startup.Tomcat.getService(Tomcat.java:412) at org.apache.catalina.startup.TomcatBaseTest.setUp(TomcatBaseTest.java:108) Best regards, Konstantin Kolinko 2012/2/2 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2700 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1239531 > Blamelist: markt > > BUILD FAILED: failed compile_1 > > sincerely, > -The Buildbot > > > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 01/02/2012 19:35, Konstantin Kolinko wrote: > The trunk Buildbot continues to display test failures since this. > > http://ci.apache.org/builders/tomcat-trunk/ > > The only failing test: > Test org.apache.catalina.websocket.TestWebSocket FAILED > > Is it supposed to succeed, or it is work in progress? > Maybe add the test to the exclusion pattern in build.xml or annotate > it with @Ignored? I'll add a dummy test with a TODO comment. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
The trunk Buildbot continues to display test failures since this. http://ci.apache.org/builders/tomcat-trunk/ The only failing test: Test org.apache.catalina.websocket.TestWebSocket FAILED Is it supposed to succeed, or it is work in progress? Maybe add the test to the exclusion pattern in build.xml or annotate it with @Ignored? Best regards, Konstantin Kolinko 2012/2/1 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2691 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1239036 > Blamelist: markt > > BUILD FAILED: failed compile_1 > > sincerely, > -The Buildbot > > > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 15/01/2012 10:35, Konstantin Kolinko wrote: > 2012/1/15 Mark Thomas : >> On 15/01/2012 06:06, Konstantin Kolinko wrote: >>> 2012/1/15 : The Buildbot has detected a new failure on builder tomcat-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tomcat-trunk/builds/2653 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: bb-vm_ubuntu Build Reason: scheduler Build Source Stamp: [branch tomcat/trunk] 1231625 Blamelist: kkolinko BUILD FAILED: failed compile_1 >>> >>> It is "org.apache.catalina.mbeans.TestRegistration FAILED" for BIO. >>> The following mbean was printed to the log before the failure: >>> [[[ >>> [junit] Jan 15, 2012 5:27:13 AM >>> org.apache.catalina.mbeans.TestRegistration testMBeanDeregistration >>> [junit] INFO: Name: >>> Tomcat:type=RequestProcessor,worker="http-bio-127.0.0.1-auto-1",name=HttpRequest1 >>> [junit] modelerType: org.apache.tomcat.util.modeler.BaseModelMBean >>> [junit] requestProcessingTime: 1326605233578 >>> [junit] bytesSent: 0 >>> [junit] rpName: >>> Tomcat:type=RequestProcessor,worker="http-bio-127.0.0.1-auto-1",name=HttpRequest1 >>> [junit] processingTime: 0 >>> [junit] errorCount: 0 >>> [junit] maxTime: 0 >>> [junit] requestBytesReceived: 0 >>> [junit] stage: 1 >>> [junit] lastRequestProcessingTime: 0 >>> [junit] globalProcessor: org.apache.coyote.RequestGroupInfo@58b51c29 >>> [junit] serverPort: -1 >>> [junit] bytesReceived: 0 >>> [junit] requestCount: 0 >>> [junit] requestBytesSent: 0 >>> [junit] contentLength: -1 >>> [junit] remoteAddr: 127.0.0.1 >>> ]]] >>> >>> So, it has remoteAddr, but it looks like nothing was received. >> >> Could this be the call to unlock the acceptor? >> > > Yes! > > 1. JIoEndpoint$Acceptor does not check "running" and "paused" flags > after accepting the socket and passes it for further processing > > 2. NioEndpoint$Acceptor checks the flags, but it seems that if > "!running" or "paused" flags are set then it does not properly close > the accepted socked thus losing it. > > 3. AprEndpoint$Acceptor seems better, > but why it checks the flags only if "deferAccept" is true? > Do we really need to start RequestProcessor and consume that OPTIONS > request sent by AbstractEndpoint.unlockAccept() ? I don't think so. I think in all cases if the endpoint is paused after the accept, we just close the socket straight away. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2012/1/15 Mark Thomas : > On 15/01/2012 06:06, Konstantin Kolinko wrote: >> 2012/1/15 : >>> The Buildbot has detected a new failure on builder tomcat-trunk while >>> building ASF Buildbot. >>> Full details are available at: >>> http://ci.apache.org/builders/tomcat-trunk/builds/2653 >>> >>> Buildbot URL: http://ci.apache.org/ >>> >>> Buildslave for this Build: bb-vm_ubuntu >>> >>> Build Reason: scheduler >>> Build Source Stamp: [branch tomcat/trunk] 1231625 >>> Blamelist: kkolinko >>> >>> BUILD FAILED: failed compile_1 >>> >> >> It is "org.apache.catalina.mbeans.TestRegistration FAILED" for BIO. >> The following mbean was printed to the log before the failure: >> [[[ >> [junit] Jan 15, 2012 5:27:13 AM >> org.apache.catalina.mbeans.TestRegistration testMBeanDeregistration >> [junit] INFO: Name: >> Tomcat:type=RequestProcessor,worker="http-bio-127.0.0.1-auto-1",name=HttpRequest1 >> [junit] modelerType: org.apache.tomcat.util.modeler.BaseModelMBean >> [junit] requestProcessingTime: 1326605233578 >> [junit] bytesSent: 0 >> [junit] rpName: >> Tomcat:type=RequestProcessor,worker="http-bio-127.0.0.1-auto-1",name=HttpRequest1 >> [junit] processingTime: 0 >> [junit] errorCount: 0 >> [junit] maxTime: 0 >> [junit] requestBytesReceived: 0 >> [junit] stage: 1 >> [junit] lastRequestProcessingTime: 0 >> [junit] globalProcessor: org.apache.coyote.RequestGroupInfo@58b51c29 >> [junit] serverPort: -1 >> [junit] bytesReceived: 0 >> [junit] requestCount: 0 >> [junit] requestBytesSent: 0 >> [junit] contentLength: -1 >> [junit] remoteAddr: 127.0.0.1 >> ]]] >> >> So, it has remoteAddr, but it looks like nothing was received. > > Could this be the call to unlock the acceptor? > Yes! 1. JIoEndpoint$Acceptor does not check "running" and "paused" flags after accepting the socket and passes it for further processing 2. NioEndpoint$Acceptor checks the flags, but it seems that if "!running" or "paused" flags are set then it does not properly close the accepted socked thus losing it. 3. AprEndpoint$Acceptor seems better, but why it checks the flags only if "deferAccept" is true? Do we really need to start RequestProcessor and consume that OPTIONS request sent by AbstractEndpoint.unlockAccept() ? Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 15/01/2012 06:06, Konstantin Kolinko wrote: > 2012/1/15 : >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/2653 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1231625 >> Blamelist: kkolinko >> >> BUILD FAILED: failed compile_1 >> > > It is "org.apache.catalina.mbeans.TestRegistration FAILED" for BIO. > The following mbean was printed to the log before the failure: > [[[ > [junit] Jan 15, 2012 5:27:13 AM > org.apache.catalina.mbeans.TestRegistration testMBeanDeregistration > [junit] INFO: Name: > Tomcat:type=RequestProcessor,worker="http-bio-127.0.0.1-auto-1",name=HttpRequest1 > [junit] modelerType: org.apache.tomcat.util.modeler.BaseModelMBean > [junit] requestProcessingTime: 1326605233578 > [junit] bytesSent: 0 > [junit] rpName: > Tomcat:type=RequestProcessor,worker="http-bio-127.0.0.1-auto-1",name=HttpRequest1 > [junit] processingTime: 0 > [junit] errorCount: 0 > [junit] maxTime: 0 > [junit] requestBytesReceived: 0 > [junit] stage: 1 > [junit] lastRequestProcessingTime: 0 > [junit] globalProcessor: org.apache.coyote.RequestGroupInfo@58b51c29 > [junit] serverPort: -1 > [junit] bytesReceived: 0 > [junit] requestCount: 0 > [junit] requestBytesSent: 0 > [junit] contentLength: -1 > [junit] remoteAddr: 127.0.0.1 > ]]] > > So, it has remoteAddr, but it looks like nothing was received. Could this be the call to unlock the acceptor? Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2012/1/15 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2653 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1231625 > Blamelist: kkolinko > > BUILD FAILED: failed compile_1 > It is "org.apache.catalina.mbeans.TestRegistration FAILED" for BIO. The following mbean was printed to the log before the failure: [[[ [junit] Jan 15, 2012 5:27:13 AM org.apache.catalina.mbeans.TestRegistration testMBeanDeregistration [junit] INFO: Name: Tomcat:type=RequestProcessor,worker="http-bio-127.0.0.1-auto-1",name=HttpRequest1 [junit] modelerType: org.apache.tomcat.util.modeler.BaseModelMBean [junit] requestProcessingTime: 1326605233578 [junit] bytesSent: 0 [junit] rpName: Tomcat:type=RequestProcessor,worker="http-bio-127.0.0.1-auto-1",name=HttpRequest1 [junit] processingTime: 0 [junit] errorCount: 0 [junit] maxTime: 0 [junit] requestBytesReceived: 0 [junit] stage: 1 [junit] lastRequestProcessingTime: 0 [junit] globalProcessor: org.apache.coyote.RequestGroupInfo@58b51c29 [junit] serverPort: -1 [junit] bytesReceived: 0 [junit] requestCount: 0 [junit] requestBytesSent: 0 [junit] contentLength: -1 [junit] remoteAddr: 127.0.0.1 ]]] So, it has remoteAddr, but it looks like nothing was received. The requestProcessingTime value of 1326605233578 gives xx:27:13 (disrespecting my different timezone), so it occurred in the same second. BTW, last Gump failure was due to two failed Tribes tests. That is nothing new. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
I haven't tried to reproduce it yet. The following is from buildbot's stdout file: Both BIO and NIO fail the same test: [junit] Tests run: 7, Failures: 4, Errors: 0, Time elapsed: 0.175 sec [junit] Test org.apache.catalina.startup.TestWebRuleSet FAILED BTW, during the NIO run there are several NPEs like the following: [[[ [junit] SEVERE: Error processing request [junit] java.lang.NullPointerException [junit] at org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSelector.java:126) [junit] at org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.java:175) [junit] at org.apache.coyote.http11.InternalNioOutputBuffer.writeToSocket(InternalNioOutputBuffer.java:170) [junit] at org.apache.coyote.http11.InternalNioOutputBuffer.flushBuffer(InternalNioOutputBuffer.java:249) [junit] at org.apache.coyote.http11.InternalNioOutputBuffer.endRequest(InternalNioOutputBuffer.java:128) [junit] at org.apache.coyote.http11.AbstractHttp11Processor.action(AbstractHttp11Processor.java:741) [junit] at org.apache.coyote.Response.action(Response.java:170) [junit] at org.apache.coyote.Response.finish(Response.java:276) [junit] at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:277) [junit] at org.apache.catalina.connector.Response.finishResponse(Response.java:410) [junit] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:434) [junit] at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:983) [junit] at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:554) [junit] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1594) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [junit] at java.lang.Thread.run(Thread.java:662) [junit] Dec 31, 2011 10:47:53 PM org.apache.catalina.connector.CoyoteAdapter log [junit] WARNING: Exception while attempting to add an entry to the access log [junit] java.lang.NullPointerException [junit] at org.apache.catalina.connector.CoyoteAdapter.log(CoyoteAdapter.java:511) [junit] at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1003) [junit] at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:554) [junit] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1594) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [junit] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [junit] at java.lang.Thread.run(Thread.java:662) ]]] It is hard to tell to what test these NPEs belong. I suspect that they occur during shutdown. Best regards, Konstantin Kolinko 2012/1/1 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2611 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1226196 > Blamelist: markt > > BUILD FAILED: failed compile_1 > > sincerely, > -The Buildbot > > > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
should be fixed with r1209731 On 2 déc. 2011, at 22:19, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2564 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1209686 > Blamelist: slaurent > > BUILD FAILED: failed compile_1 > > sincerely, > -The Buildbot > > > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 10.11.2011 14:52, Konstantin Kolinko wrote: 2011/11/11 Rainer Jung: On 10.11.2011 13:46, build...@apache.org wrote: The Buildbot has detected a new failure on builder tomcat-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tomcat-trunk/builds/2492 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: bb-vm_ubuntu Build Reason: scheduler Build Source Stamp: [branch tomcat/trunk] 1200555 Blamelist: rjung BUILD FAILED: failed compile_1 Test failure in org.apache.catalina.tribes.group.interceptors.TestNonBlockingCoordinator. Wasn't that the test that is already known to sporadically fail? Couldn't reproduce here on first run. Will run test in a loop. I don't think the failure is due to r1200555. Yes, it is sporadic. Failed 3 or 4 times during the last week. Note, that in the same buildbot run the test occurs twice (bio+nio), but only one fails. Thanks for conforming. I had run it 40 times in a row with NIO and couldn't reproduce the failure (was on Solaris Sparc though). Regards, Rainer - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2011/11/11 Rainer Jung : > On 10.11.2011 13:46, build...@apache.org wrote: >> >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/2492 >> >> Buildbot URL: http://ci.apache.org/ >> >> Buildslave for this Build: bb-vm_ubuntu >> >> Build Reason: scheduler >> Build Source Stamp: [branch tomcat/trunk] 1200555 >> Blamelist: rjung >> >> BUILD FAILED: failed compile_1 > > Test failure in > org.apache.catalina.tribes.group.interceptors.TestNonBlockingCoordinator. > Wasn't that the test that is already known to sporadically fail? Couldn't > reproduce here on first run. Will run test in a loop. I don't think the > failure is due to r1200555. > Yes, it is sporadic. Failed 3 or 4 times during the last week. Note, that in the same buildbot run the test occurs twice (bio+nio), but only one fails. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 10.11.2011 13:46, build...@apache.org wrote: The Buildbot has detected a new failure on builder tomcat-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tomcat-trunk/builds/2492 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: bb-vm_ubuntu Build Reason: scheduler Build Source Stamp: [branch tomcat/trunk] 1200555 Blamelist: rjung BUILD FAILED: failed compile_1 Test failure in org.apache.catalina.tribes.group.interceptors.TestNonBlockingCoordinator. Wasn't that the test that is already known to sporadically fail? Couldn't reproduce here on first run. Will run test in a loop. I don't think the failure is due to r1200555. Regards, Rainer - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2011/11/3 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2453 Some ~random test failure in TestNonBlockingCoordinator [junit] Running org.apache.catalina.tribes.group.interceptors.TestNonBlockingCoordinator (...) [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 37.608 sec [junit] Test org.apache.catalina.tribes.group.interceptors.TestNonBlockingCoordinator FAILED It was first run (bio) and it failed with some timeouts. The second run (nio) was successful and several times faster: Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8.673 sec All other tests did run OK. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2011/10/31 Konstantin Kolinko : > 2011/10/31 : >> The Buildbot has detected a new failure on builder tomcat-trunk while >> building ASF Buildbot. >> Full details are available at: >> http://ci.apache.org/builders/tomcat-trunk/builds/2442 >> > > [junit] Running org.apache.tomcat.util.http.mapper.TestMapper > [junit] Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 4.682 sec > [junit] Test org.apache.tomcat.util.http.mapper.TestMapper FAILED > > There are no details wrt what test in TestMapper failed and why. Cannot reproduce. It probably was testPerformance(). Note the "4.682 sec" in the message above. The performance test takes most of the time and it fails if time taken is >= 4 sec. Another TestMapper run in the same log file is Time elapsed: 1.422 sec. Previous build (2441) also shows similar numbers of 1.47, 1.41 sec. On my laptop the TestMapper tests currently take ~3,4 sec to run. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2011/10/31 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2442 > [junit] Running org.apache.tomcat.util.http.mapper.TestMapper [junit] Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 4.682 sec [junit] Test org.apache.tomcat.util.http.mapper.TestMapper FAILED There are no details wrt what test in TestMapper failed and why. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2011/10/28 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2429 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1190185 > Blamelist: markt > > BUILD FAILED: failed compile_1 > Appears to be a NPE failure during Tomcat shutdown, in many tests. [[[ [junit] Running org.apache.catalina.comet.TestCometProcessor [junit] Tests run: 6, Failures: 0, Errors: 6, Time elapsed: 0.28 sec [junit] Oct 28, 2011 7:47:26 AM org.apache.coyote.AbstractProtocol destroy [junit] INFO: Destroying ProtocolHandler ["http-bio-8001"] [junit] Oct 28, 2011 7:47:26 AM org.apache.catalina.core.ContainerBase removeChild [junit] SEVERE: ContainerBase.removeChild: destroy: [junit] org.apache.catalina.LifecycleException: Failed to destroy component [StandardEngine[Tomcat].StandardHost[localhost]] [junit] at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:296) [junit] at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:1000) [junit] at org.apache.catalina.core.ContainerBase.destroyInternal(ContainerBase.java:1185) [junit] at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:292) [junit] at org.apache.catalina.core.StandardService.destroyInternal(StandardService.java:572) [junit] at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:292) [junit] at org.apache.catalina.core.StandardServer.destroyInternal(StandardServer.java:770) [junit] at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:292) [junit] at org.apache.catalina.startup.Tomcat.destroy(Tomcat.java:355) [junit] at org.apache.catalina.startup.TomcatBaseTest.tearDown(TomcatBaseTest.java:211) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [junit] at java.lang.reflect.Method.invoke(Method.java:597) [junit] at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) [junit] at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) [junit] at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) [junit] at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:37) [junit] at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) [junit] at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) [junit] at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) [junit] at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) [junit] at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) [junit] at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) [junit] at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) [junit] at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) [junit] at org.junit.runners.ParentRunner.run(ParentRunner.java:236) [junit] at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:39) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:518) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1052) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:906) [junit] Caused by: java.lang.NullPointerException [junit] at org.apache.catalina.core.ContainerBase.destroyInternal(ContainerBase.java:1193) [junit] at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:292) [junit] ... 30 more (...) [junit] Test org.apache.catalina.comet.TestCometProcessor FAILED ]]] ... [junit] Test org.apache.catalina.filters.TestCsrfPreventionFilter FAILED [junit] Test org.apache.catalina.filters.TestExpiresFilter FAILED etc. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
Even though it says "compile_1", it is a testsuite failure. Test org.apache.catalina.tribes.group.interceptors.TestNonBlockingCoordinator FAILED Test org.apache.catalina.tribes.group.interceptors.TestOrderInterceptor FAILED Both tests were run twice (BIO, NIO), but only the second run failed. Best regards, Konstantin Kolinko 2011/10/10 : > The Buildbot has detected a new failure on builder tomcat-trunk while > building ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/2352 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: scheduler > Build Source Stamp: [branch tomcat/trunk] 1180721 > Blamelist: markt > > BUILD FAILED: failed compile_1 > > sincerely, > -The Buildbot > > > > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 12.08.2010 00:11, Konstantin Kolinko wrote: 2010/8/12: The Buildbot has detected a new failure of tomcat-trunk on ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tomcat-trunk/builds/373 (..) BUILD FAILED: failed compile http://ci.apache.org/builders/tomcat-trunk/builds/373/steps/compile/logs/stdio says: BUILD FAILED /home/buildslave3/slave3/tomcat-trunk/build/build.xml:440: Unable to find a javac compiler; com.sun.tools.javac.Main is not on the classpath. ... and then Perhaps JAVA_HOME does not point to the JDK. It is currently set to "/usr/lib/jvm/java-6-sun-1.6.0.20/jre" That "/jre" looks suspicious (but don't know anything about buildbot). And closer to the top: Unable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-6-sun-1.6.0.20/lib/tools.jar So I'd say this shouldn't be related to Mark's latest changes. Unfortunately the path settings for Java are not part of the output. Regards, Rainer - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2010/8/12 : > The Buildbot has detected a new failure of tomcat-trunk on ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/373 > (..) > > BUILD FAILED: failed compile > http://ci.apache.org/builders/tomcat-trunk/builds/373/steps/compile/logs/stdio says: BUILD FAILED /home/buildslave3/slave3/tomcat-trunk/build/build.xml:440: Unable to find a javac compiler; com.sun.tools.javac.Main is not on the classpath. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: buildbot failure in ASF Buildbot on tomcat-trunk
> -Original Message- > From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] > Sent: Wednesday, 10 February 2010 10:36 PM > To: Tomcat Developers List > Cc: bui...@apache.org > Subject: Re: buildbot failure in ASF Buildbot on tomcat-trunk > > 2010/2/10 Gav... : > > > > > >> -Original Message- > >> From: Mark Thomas [mailto:ma...@apache.org] > >> Sent: Tuesday, 9 February 2010 8:27 PM > >> To: Tomcat Developers List > >> Cc: bui...@apache.org > >> Subject: Re: buildbot failure in ASF Buildbot on tomcat-trunk > >> > >> On 09/02/2010 10:25, build...@apache.org wrote: > >> > The Buildbot has detected a new failure of tomcat-trunk on ASF > >> Buildbot. > >> > Full details are available at: > >> > http://ci.apache.org/builders/tomcat-trunk/builds/83 > >> > > >> > Buildbot URL: http://ci.apache.org/ > >> > > >> > Buildslave for this Build: bb-vm_ubuntu > >> > > >> > Build Reason: > >> > Build Source Stamp: [branch tomcat/trunk] 907983 > >> > Blamelist: markt > >> > > >> > BUILD FAILED: failed compile > >> > >> The Eclipse download takes forever which seems to be the root cause > of > >> a > >> number of these failures. Could the build property "jdt.home" be set > to > >> somewhere that isn't deleted on every ci build? That should speed up > >> the > >> build process considerably - as well as not downloading a 25MB file > >> from > >> archive.eclipse.org every time we build. > > > > Actually, I havent set that property at all that I know of. > > In Buildbot it can be added as a property at build time so it's no > problem. > > > > Shall I go ahead and do that? > > > > What value should it be, empty? > > > > Gav... > > > > Not jdt.home, but base.path I think. > > The "base.path" property points to a location, where all dependent > libraries are downloaded from the net. > > The default value of it is > base.path=/usr/share/java > and as I see from stdio output from buildbot, there it is set to > /home/buildslave3/slave3/tomcat-trunk/build/basepath/ > > The problem is that all those dependencies are deleted before each run > and are redownloaded, which wastes time and, with a 40 MB download > from eclipse.org, resulted in intermittent failures. > > Can we avoid deleting those files between runs? > > > In the meanwhile, yesterday I changed dependencies in tomcat-trunk, > and now we are downloading a 1.6 MB file instead of 40 MB one. So, the > problem will be less noticeable for trunk now, but will still present > for "tomcat-6-trunk", where this change is not implemented yet. > > > The "tomcat-6-trunk" buildbot apparently has the same value of > "base.path" as the "tomcat-trunk" one. That is, it reuses libraries > downloaded by "tomcat-trunk" on its previous run. Thus it was more > rare to see errors coming from it. ah, ok thanks for the explanations. With builds, I prefer to keep the rest of the file system clean wherever possible, so over-riding base path was my solution. I can see that having it in the build dir can cause problems so I've just moved it one level above the main build dir so it doesnt get clobbered each run, but is still within the tomcat-trunk and tomcat-6-trunk directory structure. Thanks Gav... > > > Best regards, > Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 10/02/2010 12:35, Konstantin Kolinko wrote: > Not jdt.home, but base.path I think. No, I meant jdt.home. I was only looking to keep JDT between builds. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2010/2/10 Gav... : > > >> -Original Message- >> From: Mark Thomas [mailto:ma...@apache.org] >> Sent: Tuesday, 9 February 2010 8:27 PM >> To: Tomcat Developers List >> Cc: bui...@apache.org >> Subject: Re: buildbot failure in ASF Buildbot on tomcat-trunk >> >> On 09/02/2010 10:25, build...@apache.org wrote: >> > The Buildbot has detected a new failure of tomcat-trunk on ASF >> Buildbot. >> > Full details are available at: >> > http://ci.apache.org/builders/tomcat-trunk/builds/83 >> > >> > Buildbot URL: http://ci.apache.org/ >> > >> > Buildslave for this Build: bb-vm_ubuntu >> > >> > Build Reason: >> > Build Source Stamp: [branch tomcat/trunk] 907983 >> > Blamelist: markt >> > >> > BUILD FAILED: failed compile >> >> The Eclipse download takes forever which seems to be the root cause of >> a >> number of these failures. Could the build property "jdt.home" be set to >> somewhere that isn't deleted on every ci build? That should speed up >> the >> build process considerably - as well as not downloading a 25MB file >> from >> archive.eclipse.org every time we build. > > Actually, I haven’t set that property at all that I know of. > In Buildbot it can be added as a property at build time so it's no problem. > > Shall I go ahead and do that? > > What value should it be, empty? > > Gav... > Not jdt.home, but base.path I think. The "base.path" property points to a location, where all dependent libraries are downloaded from the net. The default value of it is base.path=/usr/share/java and as I see from stdio output from buildbot, there it is set to /home/buildslave3/slave3/tomcat-trunk/build/basepath/ The problem is that all those dependencies are deleted before each run and are redownloaded, which wastes time and, with a 40 MB download from eclipse.org, resulted in intermittent failures. Can we avoid deleting those files between runs? In the meanwhile, yesterday I changed dependencies in tomcat-trunk, and now we are downloading a 1.6 MB file instead of 40 MB one. So, the problem will be less noticeable for trunk now, but will still present for "tomcat-6-trunk", where this change is not implemented yet. The "tomcat-6-trunk" buildbot apparently has the same value of "base.path" as the "tomcat-trunk" one. That is, it reuses libraries downloaded by "tomcat-trunk" on its previous run. Thus it was more rare to see errors coming from it. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: buildbot failure in ASF Buildbot on tomcat-trunk
> -Original Message- > From: Mark Thomas [mailto:ma...@apache.org] > Sent: Tuesday, 9 February 2010 8:27 PM > To: Tomcat Developers List > Cc: bui...@apache.org > Subject: Re: buildbot failure in ASF Buildbot on tomcat-trunk > > On 09/02/2010 10:25, build...@apache.org wrote: > > The Buildbot has detected a new failure of tomcat-trunk on ASF > Buildbot. > > Full details are available at: > > http://ci.apache.org/builders/tomcat-trunk/builds/83 > > > > Buildbot URL: http://ci.apache.org/ > > > > Buildslave for this Build: bb-vm_ubuntu > > > > Build Reason: > > Build Source Stamp: [branch tomcat/trunk] 907983 > > Blamelist: markt > > > > BUILD FAILED: failed compile > > The Eclipse download takes forever which seems to be the root cause of > a > number of these failures. Could the build property "jdt.home" be set to > somewhere that isn't deleted on every ci build? That should speed up > the > build process considerably - as well as not downloading a 25MB file > from > archive.eclipse.org every time we build. Actually, I haven’t set that property at all that I know of. In Buildbot it can be added as a property at build time so it's no problem. Shall I go ahead and do that? What value should it be, empty? Gav... > > Mark > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
On 09/02/2010 10:25, build...@apache.org wrote: > The Buildbot has detected a new failure of tomcat-trunk on ASF Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/83 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: > Build Source Stamp: [branch tomcat/trunk] 907983 > Blamelist: markt > > BUILD FAILED: failed compile The Eclipse download takes forever which seems to be the root cause of a number of these failures. Could the build property "jdt.home" be set to somewhere that isn't deleted on every ci build? That should speed up the build process considerably - as well as not downloading a 25MB file from archive.eclipse.org every time we build. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2010/2/7 Gav... : > > I know I still need to add JDK 5 for Tomcat 6 'ant download' to complete. > Yes. Tomcat 6 has to be built with JDK 5. > There was mention of making the produced builds available. > > Can you let me know what builds you want making available and I'll get on > with it? > > Probably the contents of output/release ? or just the contents of > output/release/v7.0.0-dev/src/ ? > I think it is output/release Both the binaries and the sources are needed. > What else? > > Thanks > > Gav... > Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: buildbot failure in ASF Buildbot on tomcat-trunk
> -Original Message- > From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] > Sent: Sunday, 7 February 2010 12:22 PM > To: Tomcat Developers List > Subject: Re: buildbot failure in ASF Buildbot on tomcat-trunk > > 2010/2/7 Gav... : > >> > >> as mentioned I have upped the allocation to: > >> > >> 'ANT_OPTS': '-Xms128m -Xmx768m -XX:MaxPermSize=256m > >> > > Hi, Gavin! > > 1. Looking at stdout for compile, compile_1, compile_2, compile_3 in > http://ci.apache.org/builders/tomcat-trunk/builds/57 > > I see that ANT_OPTS setting is mentioned only in compile_1, but not in > the three other ones. yeah, I'm a dumbass, should have set it on the entire builder, not just the first step, fixed now and the build now passes, thanks! > > > 2. In the recent updates to the trunk build files Mark not only merged > our three build files into build.xml, but also configured the > dependencies. To build TC trunk release now it is sufficient to call > "ant release" and it will perform all the steps: download, > compilation, compilation of extra, bundling the release. Ah, excellent, I didn't dig into the changes enough, I've now wiped the previous steps, thanks again. Right then, we can move on to the next stages. I know I still need to add JDK 5 for Tomcat 6 'ant download' to complete. There was mention of making the produced builds available. Can you let me know what builds you want making available and I'll get on with it? Probably the contents of output/release ? or just the contents of output/release/v7.0.0-dev/src/ ? What else? Thanks Gav... > > It can be seen from compile_3 output: it does download, compilation, > and then fails from OutOfMemory. > > Thus the configuration for building the trunk can be simplified. > > The build procedure for Tomcat 6 remains the same. > > > > Thank you for your work on this. > > Best regards, > Konstantin Kolinko > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in ASF Buildbot on tomcat-trunk
2010/2/7 Gav... : >> >> as mentioned I have upped the allocation to: >> >> 'ANT_OPTS': '-Xms128m -Xmx768m -XX:MaxPermSize=256m >> Hi, Gavin! 1. Looking at stdout for compile, compile_1, compile_2, compile_3 in http://ci.apache.org/builders/tomcat-trunk/builds/57 I see that ANT_OPTS setting is mentioned only in compile_1, but not in the three other ones. 2. In the recent updates to the trunk build files Mark not only merged our three build files into build.xml, but also configured the dependencies. To build TC trunk release now it is sufficient to call "ant release" and it will perform all the steps: download, compilation, compilation of extra, bundling the release. It can be seen from compile_3 output: it does download, compilation, and then fails from OutOfMemory. Thus the configuration for building the trunk can be simplified. The build procedure for Tomcat 6 remains the same. Thank you for your work on this. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: buildbot failure in ASF Buildbot on tomcat-trunk
Also, I'll be on the #tomcat irc if anyone wants to go through this with me. Gav... > -Original Message- > From: Gav... [mailto:ga...@16degrees.com.au] > Sent: Sunday, 7 February 2010 10:44 AM > To: 'Tomcat Developers List' > Subject: RE: buildbot failure in ASF Buildbot on tomcat-trunk > > Well I have no clue, > > as mentioned I have upped the allocation to: > > 'ANT_OPTS': '-Xms128m -Xmx768m -XX:MaxPermSize=256m > > Does anyone else have problems running 'ant release' ? > > In the meantime, I'll alter the buildbot config to > only send notifications when state of the build has > changed from pass to fail, fail to pass. > > Gav... > > > > -Original Message- > > From: build...@apache.org [mailto:build...@apache.org] > > Sent: Sunday, 7 February 2010 11:25 AM > > To: dev@tomcat.apache.org > > Subject: buildbot failure in ASF Buildbot on tomcat-trunk > > > > The Buildbot has detected a failed build of tomcat-trunk on ASF > > Buildbot. > > Full details are available at: > > http://ci.apache.org/builders/tomcat-trunk/builds/58 > > > > Buildbot URL: http://ci.apache.org/ > > > > Buildslave for this Build: bb-vm_ubuntu > > > > Build Reason: forced: by IRC user on channel #asftest: > > testing increase of mem to ant_opts > > Build Source Stamp: HEAD > > Blamelist: > > > > BUILD FAILED: failed compile_3 > > > > sincerely, > > -The ASF Buildbot > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: buildbot failure in ASF Buildbot on tomcat-trunk
Well I have no clue, as mentioned I have upped the allocation to: 'ANT_OPTS': '-Xms128m -Xmx768m -XX:MaxPermSize=256m Does anyone else have problems running 'ant release' ? In the meantime, I'll alter the buildbot config to only send notifications when state of the build has changed from pass to fail, fail to pass. Gav... > -Original Message- > From: build...@apache.org [mailto:build...@apache.org] > Sent: Sunday, 7 February 2010 11:25 AM > To: dev@tomcat.apache.org > Subject: buildbot failure in ASF Buildbot on tomcat-trunk > > The Buildbot has detected a failed build of tomcat-trunk on ASF > Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/58 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: forced: by IRC user on channel #asftest: > testing increase of mem to ant_opts > Build Source Stamp: HEAD > Blamelist: > > BUILD FAILED: failed compile_3 > > sincerely, > -The ASF Buildbot > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
