You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Igal Sapir <ig...@lucee.org> on 2018/10/23 05:08:22 UTC
Re: buildbot failure in on tomcat-trunk
I am able to build locally on that same revision.
Any ideas?
Igal
On Mon, Oct 22, 2018 at 9:51 PM <bu...@apache.org> wrote:
> The Buildbot has detected a new failure on builder tomcat-trunk while
> building . Full details are available at:
> https://ci.apache.org/builders/tomcat-trunk/builds/3677
>
> Buildbot URL: https://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] 1844615
> Blamelist: isapir
>
> BUILD FAILED: failed compile_1
>
> Sincerely,
> -The Buildbot
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
Re: buildbot failure in on tomcat-trunk
Posted by Igal Sapir <ig...@lucee.org>.
Rainer,
On Tue, Oct 23, 2018 at 1:03 AM Rainer Jung <ra...@kippdata.de> wrote:
> Am 23.10.2018 um 07:08 schrieb Igal Sapir:
> > I am able to build locally on that same revision.
> >
> > Any ideas?
>
> You can see the reason by looking at the link included in the mail:
>
> https://ci.apache.org/builders/tomcat-trunk/builds/3677
>
> On that page there's a red entry for "compile_1" and a link to its
> "stdio" (output text):
>
I got to the link above, but I didn't see the link to the below until you
pointed it out, thanks.
>
>
> https://ci.apache.org/builders/tomcat-trunk/builds/3677/steps/compile_1/logs/stdio
>
> That large output shows at the end, that running the tests failed for
> TEST-org.apache.catalina.connector.TestCoyoteOutputStream.NIO2.txt
>
> Running the tests is part of the build bot compile_1 step.
>
Understood. I only modified the documentation so I tested with `ant
build-docs` and `ant clean deploy`. It makes sense though.
> I always forget where to find the detailed per test run output files.
> But I vaguely remember, that this specific test (TestCoyoteOutputStream
> for NIO2) sometimes fails for yet to be determined reasons.
>
There is a suggestion to search for "ERROR" in the logs, but there is a
test case that produces a log entry with "MUST_ERROR", which is a false
positive. I wonder if we can change that?
[junit] Exception in thread "testBug54928"
java.lang.IllegalStateException: Calling [asyncComplete()] is not
valid for a request with Async state [MUST_ERROR]
> And the following build again succeeded.
>
Is there a way to trigger a new build without a commit, or should I try a
"dummy" commit to trigger a build if I suspect that there was an
intermittent problem with a test case?
Thank you,
Igal
> Regards,
>
> Rainer
>
>
> > On Mon, Oct 22, 2018 at 9:51 PM <bu...@apache.org> wrote:
> >
> >> The Buildbot has detected a new failure on builder tomcat-trunk while
> >> building . Full details are available at:
> >> https://ci.apache.org/builders/tomcat-trunk/builds/3677
> >>
> >> Buildbot URL: https://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] 1844615
> >> Blamelist: isapir
> >>
> >> BUILD FAILED: failed compile_1
> >>
> >> Sincerely,
> >> -The Buildbot
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
Re: buildbot failure in on tomcat-trunk
Posted by Rainer Jung <ra...@kippdata.de>.
Am 23.10.2018 um 07:08 schrieb Igal Sapir:
> I am able to build locally on that same revision.
>
> Any ideas?
You can see the reason by looking at the link included in the mail:
https://ci.apache.org/builders/tomcat-trunk/builds/3677
On that page there's a red entry for "compile_1" and a link to its
"stdio" (output text):
https://ci.apache.org/builders/tomcat-trunk/builds/3677/steps/compile_1/logs/stdio
That large output shows at the end, that running the tests failed for
TEST-org.apache.catalina.connector.TestCoyoteOutputStream.NIO2.txt
Running the tests is part of the build bot compile_1 step.
I always forget where to find the detailed per test run output files.
But I vaguely remember, that this specific test (TestCoyoteOutputStream
for NIO2) sometimes fails for yet to be determined reasons.
And the following build again succeeded.
Regards,
Rainer
> On Mon, Oct 22, 2018 at 9:51 PM <bu...@apache.org> wrote:
>
>> The Buildbot has detected a new failure on builder tomcat-trunk while
>> building . Full details are available at:
>> https://ci.apache.org/builders/tomcat-trunk/builds/3677
>>
>> Buildbot URL: https://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] 1844615
>> Blamelist: isapir
>>
>> BUILD FAILED: failed compile_1
>>
>> Sincerely,
>> -The Buildbot
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org