Re: [Scons-dev] CI Roadmap: ( Was Enabling Travis CI service for SCons on github)

2017-12-20 Thread Bill Deegan
I'm using: PYTHONPATH=$PWD/QMTest:$PWD/src/engine:$PWD/testing/framework python src/engine/SCons/EnvironmentValuesSubstTests.py In my current sandbox. Most unit tests (under src/engine) are runnable that way. The tests under test/... may not be as easy to run without runtest.py. Still

Re: [Scons-dev] CI Roadmap: ( Was Enabling Travis CI service for SCons on github)

2017-12-20 Thread Andrew Featherstone
Are you able to provide a one liner that helps clarify this? python -m unittest discover -s QMTest --pattern "Test*.py" produces a very quick failure. Andrew On 20 December 2017 at 16:39, Bill Deegan wrote: > 4. We're already using unittest. QMtest is just the name

Re: [Scons-dev] CI Roadmap: ( Was Enabling Travis CI service for SCons on github)

2017-12-20 Thread Bill Deegan
4. We're already using unittest. QMtest is just the name of the directory at this point. (You used to have to install qmtest to run the test suite) On Wed, Dec 20, 2017 at 11:28 AM, Daniel Moody wrote: > 1. are you referring to the use of runtest.py command, or how the

Re: [Scons-dev] CI Roadmap: ( Was Enabling Travis CI service for SCons on github)

2017-12-20 Thread Daniel Moody
1. are you referring to the use of runtest.py command, or how the various builders and environments are started? 2. agreed 3. With the free CI services you are limited to whatever they offer, and at this point splitting up the tests is a workaround, instead of rewriting the entire test suite. Even

[Scons-dev] CI Roadmap: ( Was Enabling Travis CI service for SCons on github)

2017-12-20 Thread Bill Deegan
On Wed, Dec 20, 2017 at 11:05 AM, Andrew Featherstone < andrew.featherst...@cantab.net> wrote: > My preferred way of working on this problem: > > >1. Get parity with what happens at http://buildbot.scons.org/#/. I >can't work out from there how to read the actual commands being run in the