Master is not passing all tests for Windows, and some tests aren't even run if the binaries aren't installed in the CI environment, there plenty of room for improvemnt. The CI is more to raise a flag and examine the failing tests. If they aren't related or it's something unrelated to the PR, then it's ok.
In PR 3129, the latest build seems to have had a connection issue from the VM running the tests. An owner of the repo can rerun the tests, but they seem unrelated to your PR. On Wed, May 30, 2018, 3:33 PM Jason Kenny <dragon...@live.com> wrote: > > Hi, > > It looks like the CI is messed up ( ie stuck or something). It also looks > like there are a number of testing issues on master as it is today. I > change my code to basically add nothing to validate this. How should this > go forward? Do we need all these failing tests passing on the CI? > > Jason > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev
