Actually there are several that are passing in the build history after the patch.
The issue for the ones that are failing is that JobsTest.py is intermittently failing. I tried to do a workaround that retried the test 10 times, but sometimes it just continually fails. I think it's because of the VM environment that travis uses. I was thinking instead of trying to workaround it, we could ignore failures while in the CI environments. On Feb 19, 2018 2:49 PM, "Bill Deegan" <b...@baddogconsulting.com> wrote: > This one: > https://travis-ci.org/SCons/scons/jobs/343424806 > (or any since we put in the patch to bump the pickle version up in order > to fix the py3.* builds) > > On Mon, Feb 19, 2018 at 2:42 PM, Daniel Moody <dmoody...@gmail.com> wrote: > >> The double bar (||) means execute the next command on non zero exit from >> previous command. So if there is exit 1 or 2, then it checks if 2, which >> means that it was only no results, which is considered passing. If there is >> a 1 exitcode then it fails. >> >> Do you have a specific travis build in question? >> >> >> On Feb 19, 2018 2:37 PM, "Bill Deegan" <b...@baddogconsulting.com> wrote: >> >>> Daniel, >>> >>> I think it's this line in the .travis.yml >>> >>> What do you expect: >>> - python runtest.py -a --exclude-list exclude_jobtest || if [[ $? == 2 >>> ]]; then true; else false; fi >>> >>> >>> Do? >>> >>> Here's what I see with a simple test in my bash shell: >>> $ echo "BILL" >>> BILL >>> $ echo $? >>> 0 >>> $ if [[ $? == 2 ]]; then true; else false; fi >>> $ echo $? >>> 1 >>> >>> >>> >>> -Bill >>> >> >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
