Last modified: 2012-10-15 21:00:31 UTC
I have a job set up at https://integration.mediawiki.org/ci/job/Parsoid-parserTests/? which is pretty great. But I'm stuck on it. The past few builds have failed due to an unknown error, and this is after I hacked around a bunch of other issues. That's fine and all, but mostly I just want it to run :) The goal is to auto-trivial-rebase a patch, for two reasons: One, it's nice to keep the code up to date, and two, if the patch is based on an old master, we'll get incorrect results in the second step of the tests (which compares test results from master and from the new patch). If someone has an idea, feel free to play around with it. If you need help, posting here or pinging me on Freenode (marktraceur) would be great.
Will attempt to poke this bug this week.
Thanks, Antoine!
In console log : https://integration.mediawiki.org/ci/job/Parsoid-parserTests/38/console The last lines executed correspond to: DIDITWORK=`echo $RBRESULT | grep "Current branch master is up to date."` Whenever grep does not match, it will exit with status 1 which makes the shell script to abort (set -e). Example: $ echo "foo" | grep bar ; echo $? 1 $ A hacky way would be to add a '|| true' at the end of command: $ echo "foo" | grep bar || true; echo $? 0 $ Or in your context: DIDITWORK=`echo $RBRESULT | grep "Current branch master is up to date."` Hope this help :-D
https://integration.mediawiki.org/ci/job/Parsoid-parserTests-getResults/36/console Now it's almost working, but apparently the Jenkins instance isn't resolving the labs instance's address. I can get the listed URI just fine, but Jenkins can't.
Done! Sorry about the delay.
