Hm. That’s a very slow test, but not 30 minutes slow. And it’s my test. I guess I should take a look.
> On Aug 10, 2016, at 11:01, Mishal Shah <[email protected]> wrote: > > Hi Jordan, > > The job is configured to timeout if it does not show any activity on the > console. In the PR build, we are seeing last test passed was 9:57am (PST) and > Jenkins killed the job at 10:27am due to no activity for 30mins. > > 09:57:21 PASS: Swift(linux-x86_64) :: Driver/many-inputs.swift (1666 of 8458) > 10:27:21 Build timed out (after 30 minutes). Marking the build as failed. > 10:27:21 Build was aborted > > This might be because of test getting stuck. > > Thanks, > Mishal Shah >> On Aug 10, 2016, at 10:49 AM, Jordan Rose <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hey, all. Any idea why the Linux bots would be timing out? (including my >> pull request testing <https://ci.swift.org/job/swift-PR-Linux/3389/>). I can >> see builds possibly taking longer than 30 minutes, but I wouldn’t expect the >> tests to do so, particularly not without the "long tests” enabled. >> >> Jordan >
_______________________________________________ swift-dev mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-dev
