Re: buildbot failure in on tomcat-9-trunk
Not a Tomcat issue. repository.a.o is timing out Mark On 05/06/2020 10:06, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-9-trunk while > building tomcat. Full details are available at: > https://ci.apache.org/builders/tomcat-9-trunk/builds/272 > > Buildbot URL: https://ci.apache.org/ > > Buildslave for this Build: asf946_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-9-commit' > triggered this build > Build Source Stamp: [branch 9.0.x] 923995d1d110a46fcfa35f3e9f90feeab79806c0 > Blamelist: Mark Thomas > > BUILD FAILED: failed shell_11 > > 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 on tomcat-9-trunk
On Thu, Apr 23, 2020 at 12:02 PM Mark Thomas wrote: > On 22/04/2020 22:53, build...@apache.org wrote: > > The Buildbot has detected a new failure on builder tomcat-9-trunk while > building tomcat. Full details are available at: > > https://ci.apache.org/builders/tomcat-9-trunk/builds/193 > > This is bizarre. > > There are two failures but the really interesting one is this one: > > > https://ci.apache.org/projects/tomcat/tomcat9/logs/193/TEST-org.apache.coyote.http2.TestAsyncTimeout.NIO.txt > > The unprintable characters in the output are all 0x00. > > The buffer is 8192 bytes in size. > > This write starts at position 8032 rather than 0. > > The stack trace indicates buffer overflow. But... > > Line 819 of OutputBuffer explicitly checks for the remaining space and > so should avoid this issue. > > There is a single test in this class and Ant is configured to use a new > JVM for evert test class so this is the first and only request to be > processed by this JVM. Therefore: > - a failure in clean-up after re-use cannot be the root cause as there > are no prior requests; > - I don't see a code path where the position can be anything other than > zero when the writes start. > > If arrayOffset was not zero that might explain the behaviour but > CharBuffer.allocate(size) is documented to return a CharBuffer with > arrayOffset of zero. > > I'm running out of explanations that don't involve rare JVM bugs, faulty > hardware, etc. > > Anyone got any ideas? > I think it's good to check failures (I do it often), but it's hard to come up with something here. Usually problems don't occur in the Catalina connector, which has been stable for a long while. Odd. So the only possible explanation besides "rare JVM bugs, faulty hardware" is a concurrent write, which is not protected against [that is normal, since it usually won't work even if you take out IO corruption]. But I don't really see a way to get into a concurrent write here. Rémy > > Mark > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
Re: buildbot failure in on tomcat-9-trunk
On 22/04/2020 22:53, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-9-trunk while > building tomcat. Full details are available at: > https://ci.apache.org/builders/tomcat-9-trunk/builds/193 This is bizarre. There are two failures but the really interesting one is this one: https://ci.apache.org/projects/tomcat/tomcat9/logs/193/TEST-org.apache.coyote.http2.TestAsyncTimeout.NIO.txt The unprintable characters in the output are all 0x00. The buffer is 8192 bytes in size. This write starts at position 8032 rather than 0. The stack trace indicates buffer overflow. But... Line 819 of OutputBuffer explicitly checks for the remaining space and so should avoid this issue. There is a single test in this class and Ant is configured to use a new JVM for evert test class so this is the first and only request to be processed by this JVM. Therefore: - a failure in clean-up after re-use cannot be the root cause as there are no prior requests; - I don't see a code path where the position can be anything other than zero when the writes start. If arrayOffset was not zero that might explain the behaviour but CharBuffer.allocate(size) is documented to return a CharBuffer with arrayOffset of zero. I'm running out of explanations that don't involve rare JVM bugs, faulty hardware, etc. Anyone got any ideas? Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in on tomcat-9-trunk
On 02/03/2020 21:21, build...@apache.org wrote: > The Buildbot has detected a new failure on builder tomcat-9-trunk while > building tomcat. Full details are available at: > https://ci.apache.org/builders/tomcat-9-trunk/builds/77 > > Buildbot URL: https://ci.apache.org/ > > Buildslave for this Build: asf946_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-9-commit' > triggered this build > Build Source Stamp: [branch 9.0.x] 711b41246ccea8fc91b156dba459991902442179 > Blamelist: Mark Thomas > > BUILD FAILED: failed compile_1 Looks like someone / something was changing the system clock during the test. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in on tomcat-9-trunk
On Mon, Feb 3, 2020 at 11:56 AM Rémy Maucherat wrote: > On Mon, Feb 3, 2020 at 8:38 AM Martin Grigorov > wrote: > >> Hi, >> >> The build failure is not related to my changes. >> Similar failure has happened few weeks ago: >> https://ci.apache.org/builders/tomcat-9-trunk/builds/12/ >> > > Due to the series of random test failures problems with HTTP/2 and NIO2 in > the past, I now have the habit of always checking every single failure. So > you don't need to put out a "not my fault" email in that case, it's not > you. It is a "known" recurrent failure with multicast it seems, I don't get > it personally. > I've sent the email so that the team knows that I've checked the build failure, i.e. that I care that my changes don't break something else :-) Thanks for all your work on Tomcat, Rémy! > Rémy > > >> >> Martin >> >> On Mon, Feb 3, 2020 at 9:20 AM wrote: >> >>> The Buildbot has detected a new failure on builder tomcat-9-trunk while >>> building tomcat. Full details are available at: >>> https://ci.apache.org/builders/tomcat-9-trunk/builds/24 >>> >>> Buildbot URL: https://ci.apache.org/ >>> >>> Buildslave for this Build: asf946_ubuntu >>> >>> Build Reason: The AnyBranchScheduler scheduler named >>> 'on-tomcat-9-commit' triggered this build >>> Build Source Stamp: [branch 9.0.x] >>> 58a490bfa7429d33cd3437b8470569daa7d9be30 >>> Blamelist: Martin Tzvetanov Grigorov >>> >>> 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 on tomcat-9-trunk
On Mon, Feb 3, 2020 at 8:38 AM Martin Grigorov wrote: > Hi, > > The build failure is not related to my changes. > Similar failure has happened few weeks ago: > https://ci.apache.org/builders/tomcat-9-trunk/builds/12/ > Due to the series of random test failures problems with HTTP/2 and NIO2 in the past, I now have the habit of always checking every single failure. So you don't need to put out a "not my fault" email in that case, it's not you. It is a "known" recurrent failure with multicast it seems, I don't get it personally. Rémy > > Martin > > On Mon, Feb 3, 2020 at 9:20 AM wrote: > >> The Buildbot has detected a new failure on builder tomcat-9-trunk while >> building tomcat. Full details are available at: >> https://ci.apache.org/builders/tomcat-9-trunk/builds/24 >> >> Buildbot URL: https://ci.apache.org/ >> >> Buildslave for this Build: asf946_ubuntu >> >> Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-9-commit' >> triggered this build >> Build Source Stamp: [branch 9.0.x] >> 58a490bfa7429d33cd3437b8470569daa7d9be30 >> Blamelist: Martin Tzvetanov Grigorov >> >> 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 on tomcat-9-trunk
Hi, The build failure is not related to my changes. Similar failure has happened few weeks ago: https://ci.apache.org/builders/tomcat-9-trunk/builds/12/ Martin On Mon, Feb 3, 2020 at 9:20 AM wrote: > The Buildbot has detected a new failure on builder tomcat-9-trunk while > building tomcat. Full details are available at: > https://ci.apache.org/builders/tomcat-9-trunk/builds/24 > > Buildbot URL: https://ci.apache.org/ > > Buildslave for this Build: asf946_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-9-commit' > triggered this build > Build Source Stamp: [branch 9.0.x] 58a490bfa7429d33cd3437b8470569daa7d9be30 > Blamelist: Martin Tzvetanov Grigorov > > 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 > >
