Seems that the commit causes one of the tests (likely stack tests?) to hang indefinitely. I'd suggest running the build on a local machine and doing a binary-elimination-search to see if you can reproduce/track down the issue.
On Mon, 2015-07-06 at 16:39 +0000, Light, John J wrote: > Erich, > > While refreshing the page showed more lines, they are problematic. Now I get > the following, which got over the weekend: > > [ PASSED ] 119 tests. > > YOU HAVE 57 DISABLED TESTS > > Build timed out (after 61 minutes). Marking the build as aborted. > Build was aborted > > I have no clue how to make Jenkins work here. > > John > > -----Original Message----- > From: Keane, Erich > Sent: Monday, July 06, 2015 9:31 AM > To: Light, John J > Cc: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] My Jenkins build had a Proxy Error > > It happens when behind the corporate network when you have the 'auto refresh' > on. If you refresh the page, it will still be continuing, this isn't a > problem with the build, just wtih the auto-refresh feature of jenkins. > > > On Mon, 2015-07-06 at 16:29 +0000, Light, John J wrote: > > Build 4042 got: > > > > > > > > > > Proxy Error > > > > > > The proxy server received an invalid > > > > response from an upstream server. > > > > > > > > The proxy server could not handle the request POST > > /ci/job/Verify-IoTivity-Scons/4042/logText/progressiveHtml. > > > > > > > > Reason: Error reading from remote server > > > > > > > > > > _______________________________________________ > > iotivity-dev mailing list > > iotivity-dev at lists.iotivity.org > > https://lists.iotivity.org/mailman/listinfo/iotivity-dev >
