You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@shindig.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2013/10/16 18:05:51 UTC
Jenkins build became unstable: Shindig 2.5.0-updateX (JDK 1.7) » Apache Shindig Web App #9
See <https://builds.apache.org/job/Shindig%202.5.0-updateX%20(JDK%201.7)/org.apache.shindig$shindig-server/9/changes>
Re: Jenkins build became unstable: Shindig 2.5.0-updateX (JDK 1.7) » Apache Shindig Web App #9
Posted by Ryan Baxter <rb...@gmail.com>.
The fact that Jetty actually responds with a 404 makes me think the
server starts. But yeah maybe it is the something about the host the
build is running on...
On Wed, Oct 16, 2013 at 8:49 PM, Stanton Sievers <ss...@apache.org> wrote:
> Is there a timing issue between when Jetty comes up with the WAR deployed
> and when we try to execute the tests? Every end-to-end test failed with a
> 404, yet based on the logs Shindig starts at some point... although it
> appears to have been too late. The last two builds (#10 & #9) ran on one
> host while the previous successful build ran on another one.
>
> -Stanton
>
>
> On Wed, Oct 16, 2013 at 8:33 PM, Ryan Baxter <rb...@apache.org> wrote:
>
>> Anyone have any thoughts as to why we are seeing the end to end tests
>> fail on builds.a.o? They seem to fail randomly...
>>
>>
>> ---------- Forwarded message ----------
>> From: Apache Jenkins Server <je...@builds.apache.org>
>> Date: Wed, Oct 16, 2013 at 12:05 PM
>> Subject: Jenkins build became unstable: Shindig 2.5.0-updateX (JDK
>> 1.7) » Apache Shindig Web App #9
>> To: commits@shindig.apache.org
>>
>>
>> See <
>> https://builds.apache.org/job/Shindig%202.5.0-updateX%20(JDK%201.7)/org.apache.shindig$shindig-server/9/changes
>> >
>>
Re: Jenkins build became unstable: Shindig 2.5.0-updateX (JDK 1.7) » Apache Shindig Web App #9
Posted by Stanton Sievers <ss...@apache.org>.
Is there a timing issue between when Jetty comes up with the WAR deployed
and when we try to execute the tests? Every end-to-end test failed with a
404, yet based on the logs Shindig starts at some point... although it
appears to have been too late. The last two builds (#10 & #9) ran on one
host while the previous successful build ran on another one.
-Stanton
On Wed, Oct 16, 2013 at 8:33 PM, Ryan Baxter <rb...@apache.org> wrote:
> Anyone have any thoughts as to why we are seeing the end to end tests
> fail on builds.a.o? They seem to fail randomly...
>
>
> ---------- Forwarded message ----------
> From: Apache Jenkins Server <je...@builds.apache.org>
> Date: Wed, Oct 16, 2013 at 12:05 PM
> Subject: Jenkins build became unstable: Shindig 2.5.0-updateX (JDK
> 1.7) » Apache Shindig Web App #9
> To: commits@shindig.apache.org
>
>
> See <
> https://builds.apache.org/job/Shindig%202.5.0-updateX%20(JDK%201.7)/org.apache.shindig$shindig-server/9/changes
> >
>
Fwd: Jenkins build became unstable: Shindig 2.5.0-updateX (JDK 1.7) » Apache Shindig Web App #9
Posted by Ryan Baxter <rb...@apache.org>.
Anyone have any thoughts as to why we are seeing the end to end tests
fail on builds.a.o? They seem to fail randomly...
---------- Forwarded message ----------
From: Apache Jenkins Server <je...@builds.apache.org>
Date: Wed, Oct 16, 2013 at 12:05 PM
Subject: Jenkins build became unstable: Shindig 2.5.0-updateX (JDK
1.7) » Apache Shindig Web App #9
To: commits@shindig.apache.org
See <https://builds.apache.org/job/Shindig%202.5.0-updateX%20(JDK%201.7)/org.apache.shindig$shindig-server/9/changes>