Russel,
I think the alternative is TestSCons.TestSCons().detect_tool(tool). A
quick look at the source makes it look like it expects a single tool name
to be given. It seems to use an environment created for that tool and uses
its path.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
Rob Managan
On 21.01.2014 18:39, Russel Winder wrote:
It is clearly the case that TestSCons.TestSCons().where_is(toolSequence)
uses the users current PATH to search. However when the tool is actually
used, the stripped down PATH is used. This means there appears to be no
way of checking whether a test will f
On 21.01.2014 19:05, Russel Winder wrote:
I just ran all the test on Debian Unstable and got 70 no results, which
seems fine, but 9 test fails. 2 of these I understand, the others I have
no clue about:
test/Docbook/basedir/htmlchunked/htmlchunked_cmd.py
test/Docbook/basedir/htmlh
I just ran all the test on Debian Unstable and got 70 no results, which
seems fine, but 9 test fails. 2 of these I understand, the others I have
no clue about:
test/Docbook/basedir/htmlchunked/htmlchunked_cmd.py
test/Docbook/basedir/htmlhelp/htmlhelp_cmd.py
test/Docbook/bas
It is clearly the case that TestSCons.TestSCons().where_is(toolSequence)
uses the users current PATH to search. However when the tool is actually
used, the stripped down PATH is used. This means there appears to be no
way of checking whether a test will fail due to a failure to find the
executable
