Re: [Boost-testing] Possible misconfiguration for test runner Debian-Sid.

Subject: Re: [Boost-testing] Possible misconfiguration for test runner Debian-Sid.
From: Jurko Gospodnetić (jurko.gospodnetic_at_[hidden])
Date: 2012-06-15 01:56:31

   Hi.

> I found 28 files named boost-build.jam in the test runner
> workspace!  However, none of them point to /usr/share/boost-build:
>
>   jenkins_at_riemann:~/jobs/Boost-Release-Testing-64/workspace$ find . -name boost-build.jam | xargs grep /usr/share
>   jenkins_at_riemann:~/jobs/Boost-Release-Testing-64/workspace$

   Oh, sorry for begin imprecise before, but you might be checking in 
the wrong location. :-)

   When a test starts it prepares its working folder as some temporary 
folder. In this case the test first copies its prepared 'startup' folder 
to some temporary location together with all of its subfolders and then 
does all of its work from there.

   To see it just add for example a 'print(t.workdir)' command somewhere 
near the test startup and run it (after the t.settree(...) call).

   Btw. you do not need to run the whole run.py - it is enough to run 
just this one test. Just go to the tools/build/v2/test folder and run 
the startup_v2.py script directly.

   If you take the latest version from the trunk (revision [78945] or 
later will do), the test will check for the boost-build.jam file and if 
found - report clearly where it was found and what the test's working 
folder is.

> I don't know the innards of Boost.Build that well, but might it be
> that Boost.Build defaults to /usr/share/boost-build on unix if no root
> is otherwise specified?

   Nope. You can look at the test in question (startup_v2.py) for 
example. It runs Boost Build from a folder such that there should be no 
boost-build.jam in that folder or any of its parents. It then tests that 
Boost Build correctly detects and reports this with an appropriate 
end-user message.

   Hope this helps.

   Best regards,
     Jurko Gospodnetić