FYI, I built one Java 6 build with debug output enabled. Here are the logs [1]. This same issue is plaguing the Java5 and Java7 build as well. I'm trying to compare it to the builds on my Jenkins server (which work) and I don't see a difference.
Thanks, -Stanton [1] https://builds.apache.org/view/S-Z/view/Shindig/job/Shindig%20Trunk%20%28Java%206%29/10/consoleFull On Sun, Aug 5, 2012 at 1:53 AM, Henry Saputra <[email protected]>wrote: > Nope, looks like its only happening in the CI builds > > I didnt have too much detail but I'll try to get some bandwidth to > look at this next week > > - Henry > > On Sat, Aug 4, 2012 at 2:06 PM, Stanton Sievers <[email protected]> > wrote: > > Hi everyone, > > > > I'm trying to get our builds back up and running on the > > builds.apache.orgsite and am hitting some test failures. > > > > Here's a sample build: > > https://builds.apache.org/job/Shindig%20Trunk%20%28Java%206%29/2/ > > > > Here are the logs: > > > https://builds.apache.org/job/Shindig%20Trunk%20%28Java%206%29/2/consoleFull > > > > Many of the EndToEnd tests are failing with 404 errors, as if Jetty > didn't > > come up properly to run the tests. Anyone have any ideas why this might > > happen? Has anyone ever seen this when building locally? > > > > Thanks, > > -Stanton >
