3dc8ee0379Corrected a defective Boost Build configuration.py test that gets run only on non-Windows platforms.
Jurko Gospodnetić
2012-06-13 12:36:55 +0000
0c1b6c255bAdded a new, temporary, always-failing Boost Build test named collect_debug_info.py. Used to collect additional debugging information about specific test sites, e.g. Python & OS version. Currently collects information required for debugging detected configuration.py test failures. Registered expected Boost library test failures.
Jurko Gospodnetić
2012-06-13 01:02:02 +0000
347d39005cAdded a new, temporary, always-failing Boost Build test named collect_debug_info.py. Used to collect additional debugging information about specific test sites, e.g. Python & OS version. Currently collects information required for debugging detected configuration.py test failures. Registered expected Boost library test failures.
Jurko Gospodnetić
2012-06-13 01:02:02 +0000
9ec86fca3bCorrected how Boost Build's configuration.py test detects whether the current platform interprets setting an environment variable to an empty string literally or as unsetting that variable.
Jurko Gospodnetić
2012-06-13 00:17:28 +0000
344db3edc1Corrected how Boost Build's configuration.py test detects whether the current platform interprets setting an environment variable to an empty string literally or as unsetting that variable.
Jurko Gospodnetić
2012-06-13 00:17:28 +0000
7595fd910bCorrected a few Python errors that snuck trough in the previous two Boost Build configuration.py test commits.
Jurko Gospodnetić
2012-06-13 00:04:53 +0000
76fc90f65aCorrected a few Python errors that snuck trough in the previous two Boost Build configuration.py test commits.
Jurko Gospodnetić
2012-06-13 00:04:53 +0000
eb2c285ad9Corrected a bug in the Boost Build configuration.py test that was causing it to leave behind an invalid BOOST_BUILD_USER_CONFIG environment variable setting after it finishes running with a Python interpreter prior to version 2.6 (calling os.environ.pop() did not actually clear the environment variable in question).
Jurko Gospodnetić
2012-06-13 00:01:01 +0000
77ff2a2baaCorrected a bug in the Boost Build configuration.py test that was causing it to leave behind an invalid BOOST_BUILD_USER_CONFIG environment variable setting after it finishes running with a Python interpreter prior to version 2.6 (calling os.environ.pop() did not actually clear the environment variable in question).
Jurko Gospodnetić
2012-06-13 00:01:01 +0000
e5ed57e26aCorrected a bug in the Python Boost Build implementation causing its command-line parsing to fail when given an empty-string command-line parameter.
Jurko Gospodnetić
2012-06-11 23:37:53 +0000
1855af37faCorrected a bug in the Python Boost Build implementation causing its command-line parsing to fail when given an empty-string command-line parameter.
Jurko Gospodnetić
2012-06-11 23:37:53 +0000
9c205bb4efMade Boost Build ignore any received empty command-line arguments that it previously interpreted as targets. This was causing Boost Build test failures (rule path.make-UNIX called with an empty parameter) on many non-Windows platforms where empty parameters are not automatically stripped by the OS or the used Python process call implementation.
Jurko Gospodnetić
2012-06-11 23:36:26 +0000
a4bc299d04Made Boost Build ignore any received empty command-line arguments that it previously interpreted as targets. This was causing Boost Build test failures (rule path.make-UNIX called with an empty parameter) on many non-Windows platforms where empty parameters are not automatically stripped by the OS or the used Python process call implementation.
Jurko Gospodnetić
2012-06-11 23:36:26 +0000
5db647087bAdded some temporary Boost Build debugging code as a part of the effort to track down some of the mysterious Boost Build test failures reported by the Boost library regression tests (namely, how on some platforms we are encountering empty target ids). Related code enabled using the '--plinky-plonky' command-line option.
Jurko Gospodnetić
2012-06-11 13:22:17 +0000
10bb185d92Added some temporary Boost Build debugging code as a part of the effort to track down some of the mysterious Boost Build test failures reported by the Boost library regression tests (namely, how on some platforms we are encountering empty target ids). Related code enabled using the '--plinky-plonky' command-line option.
Jurko Gospodnetić
2012-06-11 13:22:17 +0000
34b5b33315Cleaned up how Boost Build's test system reports unhandled exceptions. Now no longer uses deprecated global sys.exc_* variables and prints out the exception stack trace correctly.
Jurko Gospodnetić
2012-06-11 12:53:54 +0000
357962c2f3Cleaned up how Boost Build's test system reports unhandled exceptions. Now no longer uses deprecated global sys.exc_* variables and prints out the exception stack trace correctly.
Jurko Gospodnetić
2012-06-11 12:53:54 +0000
aa71370570Corrected a Python error in the configuration.py Boost Build test script that might have caused the test to crash on startup if the surrounding environment had the 'UGNABUNGA_FOO_BAR_BAZ_FEE_FAE_FOU_FAM' environment set.
Jurko Gospodnetić
2012-06-11 02:15:09 +0000
f2fa5efbd4Corrected a Python error in the configuration.py Boost Build test script that might have caused the test to crash on startup if the surrounding environment had the 'UGNABUNGA_FOO_BAR_BAZ_FEE_FAE_FOU_FAM' environment set.
Jurko Gospodnetić
2012-06-11 02:15:09 +0000
78d1c7f9f4Removed temporary debugging code from the configuration.py Boost Build test, now made redundant by better unhandled exception handling implemented in the main Boost Build test runner script.
Jurko Gospodnetić
2012-06-11 02:13:13 +0000
e9326dbbfaRemoved temporary debugging code from the configuration.py Boost Build test, now made redundant by better unhandled exception handling implemented in the main Boost Build test runner script.
Jurko Gospodnetić
2012-06-11 02:13:13 +0000
24002030dbMade the main Boost Build test runner script correctly report unhandled and unexpected exceptions raised from specific test scripts. Before, such an exception would terminate the whole test run while now it gets cleanly reported as just another test failure. This makes Boost library regression test results correctly report any Python errors (e.g. using a Python feature not supported by the used Python version) which previously developers had no built-in way of getting feedback about.
Jurko Gospodnetić
2012-06-11 02:02:59 +0000
e4fd12cc48Made the main Boost Build test runner script correctly report unhandled and unexpected exceptions raised from specific test scripts. Before, such an exception would terminate the whole test run while now it gets cleanly reported as just another test failure. This makes Boost library regression test results correctly report any Python errors (e.g. using a Python feature not supported by the used Python version) which previously developers had no built-in way of getting feedback about.
Jurko Gospodnetić
2012-06-11 02:02:59 +0000
b8d4657d9cMade the main Boost Build test runner script not assume that successful tests will leave behind no annotations, thus making result processing with and without XML output symmetric. Before, with XML output, if a passed test left behind some annotations, they would get reported as annotations for the next failing test.
Jurko Gospodnetić
2012-06-11 01:58:05 +0000
ebfad57a2fMade the main Boost Build test runner script not assume that successful tests will leave behind no annotations, thus making result processing with and without XML output symmetric. Before, with XML output, if a passed test left behind some annotations, they would get reported as annotations for the next failing test.
Jurko Gospodnetić
2012-06-11 01:58:05 +0000
6acb36bc11Removed some 'regression' test specialized debugging code from the main Boost Build test runner script that seems to have been left behind from some debugging efforts. It would cause annotations to be displayed to the user if that test failed and no XML output was requested, while for all the other failed tests such annotations are ignored. This seems unnecessary since this output can be collected by directly running the regression.py test script, same as what is done with any other failed test.
Jurko Gospodnetić
2012-06-11 01:55:43 +0000
0d27623e84Removed some 'regression' test specialized debugging code from the main Boost Build test runner script that seems to have been left behind from some debugging efforts. It would cause annotations to be displayed to the user if that test failed and no XML output was requested, while for all the other failed tests such annotations are ignored. This seems unnecessary since this output can be collected by directly running the regression.py test script, same as what is done with any other failed test.
Jurko Gospodnetić
2012-06-11 01:55:43 +0000
05887be75aMade the main Boost Build test runner script better align its test results on screen when not run with XML output. Now the maximum test name length is no longer hardcoded.
Jurko Gospodnetić
2012-06-11 01:49:52 +0000
7b22c43f18Made the main Boost Build test runner script better align its test results on screen when not run with XML output. Now the maximum test name length is no longer hardcoded.
Jurko Gospodnetić
2012-06-11 01:49:52 +0000
34e2f59a2cMinor stylistic cleanup in the main Boost Build test runner script.
Jurko Gospodnetić
2012-06-11 01:46:24 +0000
d11b4fdde1Minor stylistic cleanup in the main Boost Build test runner script.
Jurko Gospodnetić
2012-06-11 01:46:24 +0000
bcf6b92952Stopped using the Python string.format() method in the Boost Build configuration.py test to support running that test using Python versions older than 2.6.
Jurko Gospodnetić
2012-06-11 00:26:11 +0000
8252c7ad28Stopped using the Python string.format() method in the Boost Build configuration.py test to support running that test using Python versions older than 2.6.
Jurko Gospodnetić
2012-06-11 00:26:11 +0000
b5588a25aaFix off by one error that resulted in less than the full amount of target output being output to the user.
K. Noel Belcourt
2012-06-10 23:05:25 +0000
3d7cdbc654Fix off by one error that resulted in less than the full amount of target output being output to the user.
K. Noel Belcourt
2012-06-10 23:05:25 +0000
7f65d1e113Updated Boost Build configuration.py test debugging code to re-raise any non-SystemExit unhandled exceptions as SystemExit exceptions to avoid aborting the test runner test_all.py script.
Jurko Gospodnetić
2012-06-10 16:41:22 +0000
3c37ad63e7Updated Boost Build configuration.py test debugging code to re-raise any non-SystemExit unhandled exceptions as SystemExit exceptions to avoid aborting the test runner test_all.py script.
Jurko Gospodnetić
2012-06-10 16:41:22 +0000
3c23ae405fAdded additional temporary debugging code to the Boost Build configuration.py test to help with debugging related test failures reported on different platforms.
Jurko Gospodnetić
2012-06-10 16:18:33 +0000
9f67489dceAdded additional temporary debugging code to the Boost Build configuration.py test to help with debugging related test failures reported on different platforms.
Jurko Gospodnetić
2012-06-10 16:18:33 +0000
d029652eeeTemporarily commented out all Boost Build configuratio.py test code related to setting empty-string environment variables. Part of the effort to make this test pass on all supported platforms - trying to make sure this is the part of the test causing problems on some non-Windows platforms.
Jurko Gospodnetić
2012-06-10 10:05:04 +0000
c673617df2Temporarily commented out all Boost Build configuratio.py test code related to setting empty-string environment variables. Part of the effort to make this test pass on all supported platforms - trying to make sure this is the part of the test causing problems on some non-Windows platforms.
Jurko Gospodnetić
2012-06-10 10:05:04 +0000
7211406abbUpdated the configuration.py Boost Build test to adapt to whether the platform running that test supports setting an environment variable to an empty string value. Made the same test use explicitly specified test case ids since now some of those test cases may be skipped on specific platforms.
Jurko Gospodnetić
2012-06-10 00:54:13 +0000
c668b36282Updated the configuration.py Boost Build test to adapt to whether the platform running that test supports setting an environment variable to an empty string value. Made the same test use explicitly specified test case ids since now some of those test cases may be skipped on specific platforms.
Jurko Gospodnetić
2012-06-10 00:54:13 +0000
90e7e882e7Update the Boost Build testing framework to work correctly when calling Boost Jam with arguments containing extra spaces. Such argument strings get split on whitespace characters and cause the constructed argument list to contain empty elements which code using that list was not handling correctly.
Jurko Gospodnetić
2012-06-09 23:19:07 +0000
db9fbe17bfUpdate the Boost Build testing framework to work correctly when calling Boost Jam with arguments containing extra spaces. Such argument strings get split on whitespace characters and cause the constructed argument list to contain empty elements which code using that list was not handling correctly.
Jurko Gospodnetić
2012-06-09 23:19:07 +0000
9f58e0d2daUpdated the configuration.py Boost Build test to display more detailed information about which of its test cases failed exactly. Now each test case there displays a unique identifier on stdout when run.
Jurko Gospodnetić
2012-06-09 23:02:42 +0000
d094bde508Updated the configuration.py Boost Build test to display more detailed information about which of its test cases failed exactly. Now each test case there displays a unique identifier on stdout when run.
Jurko Gospodnetić
2012-06-09 23:02:42 +0000
fc6a60ee1eMinor stylistic changes. Removed some minor code duplication.
Jurko Gospodnetić
2012-06-09 07:28:42 +0000
184ac58165Minor stylistic changes. Removed some minor code duplication.
Jurko Gospodnetić
2012-06-09 07:28:42 +0000
c851e03de3Handle signals causing early returns from select and waitpid. Should fix FreeBSD reported problem.
K. Noel Belcourt
2012-06-09 00:21:03 +0000
9ccc28c59cHandle signals causing early returns from select and waitpid. Should fix FreeBSD reported problem.
K. Noel Belcourt
2012-06-09 00:21:03 +0000
475d86e17eUpdated the Boost Build configuration.py test so it tests explicitly disabling user configuration loading and tests specifying the user configuration file using the BOOST_BUILD_USER_CONFIG environment variable. This fixes invalid test failures when the BOOST_BUILD_USER_CONFIG environment was set on the test runner machines.
Jurko Gospodnetić
2012-06-08 08:23:58 +0000
33fb05665dUpdated the Boost Build configuration.py test so it tests explicitly disabling user configuration loading and tests specifying the user configuration file using the BOOST_BUILD_USER_CONFIG environment variable. This fixes invalid test failures when the BOOST_BUILD_USER_CONFIG environment was set on the test runner machines.
Jurko Gospodnetić
2012-06-08 08:23:58 +0000
a8344266f3Add ability to limit amount of target output that is output by bjam. Added bjam argument -mx where x is the maximum amount of output to be captured from a target, in kb.
K. Noel Belcourt
2012-06-07 15:36:46 +0000
30130783cbAdd ability to limit amount of target output that is output by bjam. Added bjam argument -mx where x is the maximum amount of output to be captured from a target, in kb.
K. Noel Belcourt
2012-06-07 15:36:46 +0000
addf48943bMerge [78800] from trunk.
K. Noel Belcourt
2012-06-06 04:00:21 +0000
ee4e9e21a9Fix: correct library names of static Qt on Windows.
Jürgen Hunold
2012-06-03 15:13:05 +0000
40dcb724bfFix: correct library names of static Qt on Windows.
Jürgen Hunold
2012-06-03 15:13:05 +0000
6e89b4abacRevert commit 76862, restore FreeBSD and other unix testers that I broke with this commit.
K. Noel Belcourt
2012-06-02 18:26:35 +0000
3cf875e93bRevert commit 76862, restore FreeBSD and other unix testers that I broke with this commit.
K. Noel Belcourt
2012-06-02 18:26:35 +0000
e55e9afd86Fix typo which caused requirements of 'preprocessed' metatarget to be ignored.
Vladimir Prus
2012-05-31 08:58:43 +0000
b2666cd4faFix typo which caused requirements of 'preprocessed' metatarget to be ignored.
Vladimir Prus
2012-05-31 08:58:43 +0000
c233d5a49aReverted an accidental Boost Build user-config.jam template configuration file change introduced in revision 78710.
Jurko Gospodnetić
2012-05-28 13:48:39 +0000
cad7734c26Reverted an accidental Boost Build user-config.jam template configuration file change introduced in revision 78710.
Jurko Gospodnetić
2012-05-28 13:48:39 +0000
973fe26031Added two missing Boost library target definitions (locale & python3) to Boost Build's 'contrib/boost.jam' module.
Jurko Gospodnetić
2012-05-28 12:52:46 +0000
4740a79dd2Added two missing Boost library target definitions (locale & python3) to Boost Build's 'contrib/boost.jam' module.
Jurko Gospodnetić
2012-05-28 12:52:46 +0000
7439636bfbPolygon: removed data member from Voronoi primitives; added color member instead; removed size template parameter from the extended_int class methods.
Andrii Sydorchuk
2012-05-28 10:23:43 +0000
9cd8c77961Polygon: removed data member from Voronoi primitives; added color member instead; removed size template parameter from the extended_int class methods.
Andrii Sydorchuk
2012-05-28 10:23:43 +0000
b26297d8f3Commented two new test case ideas for Boost Build's timedata test - 'time' targets with sources representing more than one virtual target and sources representing a virtual target that gets built by multiple actions in sequence.
Jurko Gospodnetić
2012-05-27 15:10:24 +0000
e82e6469c8Commented two new test case ideas for Boost Build's timedata test - 'time' targets with sources representing more than one virtual target and sources representing a virtual target that gets built by multiple actions in sequence.
Jurko Gospodnetić
2012-05-27 15:10:24 +0000
c4c52e90a4Fix for Boost Build's time targets failing to be built when run with a msvc exe source. Now the TIME target generator marked as composing so it can correctly handle being given multiple sources as happens in this case where the EXE generator constructs a PDB file as well. This fixes Boost Build ticket #218 and makes the Boost Build timedata unit test pass when run using the msvc toolset.
Jurko Gospodnetić
2012-05-27 06:48:02 +0000
3e7d32dad0Fix for Boost Build's time targets failing to be built when run with a msvc exe source. Now the TIME target generator marked as composing so it can correctly handle being given multiple sources as happens in this case where the EXE generator constructs a PDB file as well. This fixes Boost Build ticket #218 and makes the Boost Build timedata unit test pass when run using the msvc toolset.
Jurko Gospodnetić
2012-05-27 06:48:02 +0000
6e3f389e6fFix for Boost Build testing.jam module's time action on Windows. It now no longer outputs extra quote characters when run under the Windows cmd shell and so no longer fails when Boost Build passes it an even number of sources. Updated related unit test (to see the full effect run using the Windows cmd shell and the Cygwin gcc toolset as this test still fails for other reasons when using the msvc toolset). Better commented related code.
Jurko Gospodnetić
2012-05-27 06:36:49 +0000
91ab5b9d68Fix for Boost Build testing.jam module's time action on Windows. It now no longer outputs extra quote characters when run under the Windows cmd shell and so no longer fails when Boost Build passes it an even number of sources. Updated related unit test (to see the full effect run using the Windows cmd shell and the Cygwin gcc toolset as this test still fails for other reasons when using the msvc toolset). Better commented related code.
Jurko Gospodnetić
2012-05-27 06:36:49 +0000
bd4d630f69Added a new Boost Build unit test exercising the Jam variable expansion in actions.
Jurko Gospodnetić
2012-05-27 00:00:30 +0000
aa9c7fe4deAdded a new Boost Build unit test exercising the Jam variable expansion in actions.
Jurko Gospodnetić
2012-05-27 00:00:30 +0000
2fd4ebc4ccAdded a new Boost Build unit test exercising the SPLIT_BY_CHARACTERS built-in rule.
Jurko Gospodnetić
2012-05-26 23:27:33 +0000
6a8ed0d2bbAdded a new Boost Build unit test exercising the SPLIT_BY_CHARACTERS built-in rule.
Jurko Gospodnetić
2012-05-26 23:27:33 +0000
21f7ca56c6Merging some Boost Build testing.jam module changes into the Python Boost Build port - making unit-test action work with paths containing spaces + a comment typo correction.
Jurko Gospodnetić
2012-05-26 19:11:27 +0000
1dc06ed5f6Merging some Boost Build testing.jam module changes into the Python Boost Build port - making unit-test action work with paths containing spaces + a comment typo correction.
Jurko Gospodnetić
2012-05-26 19:11:27 +0000
Jurko Gospodnetić