[build] bjam in boost/tools/build/v2/test doesn't work
Running bjam in boost/tools/build/v2/test doesn't (seem to) run build's regressions. Instead, I get: jamfile.jam:8: in modules.load rule project-root unknown in module Jamfile</F:/tmp/boost-MinGW-32/trunk/boost/t ools/build/v2/test>. F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:314: in load-jamfile F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:62: in load F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:168: in project.find F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2\build-system.jam:569: in load F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\..\kernel\modules.jam:283: in import F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\..\kernel\bootstrap.jam:14 2: in boost-build F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\boost-build.jam:14: in module scope If I run "python absolute_sources.py" (to pick that test as an example), I get very little (and it doesn't match regression test output): F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\TestCmd.py:60: Deprecation Warning: The popen2 module is deprecated. Use the subprocess module. import popen2 Am I close? I realize that build is a different animal. Are there instructions for running its tests in isolation? (Could those instructions be put in boost/tools/build/v2/index.html?) If you're reading this on the boost-build list, please CC me as I'm not subscribed. Thanks, -Jim PS: My apologies if I missed a response to this. I posted it last week on boost.
AMDG On 11/21/2010 10:36 AM, Jim Bell wrote:
Running bjam in boost/tools/build/v2/test doesn't (seem to) run build's regressions. Instead, I get:
jamfile.jam:8: in modules.load rule project-root unknown in module Jamfile</F:/tmp/boost-MinGW-32/trunk/boost/t ools/build/v2/test>. F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:314: in load-jamfile F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:62: in load F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2/build\project.jam:168: in project.find F:/tmp/boost-MinGW-32/trunk/boost/tools/build/v2\build-system.jam:569: in load F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\..\kernel\modules.jam:283: in import F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\..\kernel\bootstrap.jam:14 2: in boost-build F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\boost-build.jam:14: in module scope
If I run "python absolute_sources.py" (to pick that test as an example), I get very little (and it doesn't match regression test output): F:\tmp\boost-MinGW-32\trunk\boost\tools\build\v2\test\TestCmd.py:60: Deprecation Warning: The popen2 module is deprecated. Use the subprocess module. import popen2
That's probably related to your python version. This should work.
Am I close? I realize that build is a different animal. Are there instructions for running its tests in isolation? (Could those instructions be put in boost/tools/build/v2/index.html?)
If you're reading this on the boost-build list, please CC me as I'm not subscribed.
Thanks, -Jim
PS: My apologies if I missed a response to this. I posted it last week on boost.
In Christ, Steven Watanabe
Jim Bell wrote:
Running bjam in boost/tools/build/v2/test doesn't (seem to) run build's regressions. Instead, I get:
jamfile.jam:8: in modules.load rule project-root unknown in module
You should be using 'python test_all.py'. Running 'bjam' there is not really supposed to do anything. - Volodya
On 1:59 PM, Vladimir Prus wrote:
Jim Bell wrote:
Running bjam in boost/tools/build/v2/test doesn't (seem to) run build's regressions. Instead, I get:
jamfile.jam:8: in modules.load rule project-root unknown in module You should be using 'python test_all.py'. Running 'bjam' there is not really supposed to do anything.
Thanks! This works and gives me results like this... unit_tests : FAILED module_actions : PASSED startup_v1 : PASSED ... I see, too, that '--verbose' enables detailed output, from BoostBuild.Tester's docstring (and from trying it). But it says "Note that it does not also enable more verbose build system output like the --verbose command line option does." What does that mean? If I run "python test_all.py --verbose verbose" it doesn't seem to like that (attempts to run verbose.init). Also, I'm seeing a different pass/fail pattern between when I run it like this and when it runs from run.py. I'm running it with mingw-4.4.3 on the same trunk revision that the "MinGW-32 jc-bell.com" regression has reported. Picking "absolute_sources", for example, I see absolute_sources : PASSED But the regression shows it failed. How do I reconcile these?
participants (3)
-
Jim Bell -
Steven Watanabe -
Vladimir Prus