Opened 16 years ago
Last modified 16 years ago
#197 new enhancement
Make Boost Build's unit tests display their action's error output.
| Reported by: | Owned by: | somebody | |
|---|---|---|---|
| Priority: | major | Milestone: | M13 |
| Component: | component1 | Version: | 2.0 |
| Keywords: | Jam test output error | Cc: |
Description
Currently Boost Build unit tests do not collect error output from the actions they trigger. They do collect the standard output but not the error output.
This seems to be triggered by the -d0 Boost Jam option used by the Boost Build test system. It seems that this option caused Boost Jam to treat all actions as quiet ones and not display any output from them.
We should either change the was -d0 Boost Jam option is handled or add a new Boost Jam display output level that would cause it to be quiet and not display any standard output but display any error output.
Boost Jam's help screen (bjam --help-options) states that -d0 display output level should display all error output.
This would make it easier to understand test failures such as the one happening when you run many of Boost Build's tests (e.g. generator_test.py) with a toolset (e.g. msvc) that has an invalid folder configured and so its actions fail due to the OS not being able to find the requested compiler executable.
This could possibly have something to do with trac ticket #196.