Jenkins failing after tests passing on PPD machine
Came across a curious feature with Jenkins. I ran all the tests on the tracker_devel branch on the PPD cluster and all were passed. I pushed the branch to Launchpad, triggering a Jenkins build which then failed. I explored the workspace to try to figure out why. The build output is attached. Having checked the build_all file its seems this is the new version which pipes all the output to just the one file. It doesn't seem to hold the test output though, so I cannot debug. Also, its seems wrong that the tests should pass on one pretty standard system and fail in another.
Jenkins is causing me some consternation at present, it does not seem like I'm playing a fair game...
Updated by Rogers, Chris about 11 years ago
- Status changed from Open to Rejected
- Target version set to Future MAUS release
Looks like the recipe I invented for using tail -f is broken (I guess tail -f never finishes, so the build runs for ever). Oh well, probably means there's no simple way to do this. You just have to look in the install_log_std file (not so arduous I hope). But I don't know what else you are worried about... we can talk later.