[test] runtime failures with "main() should return report_errors()"
Hello, With the Boost.Python tests I'm observing a couple of mysterious failures, where the test application fails *after* the actual test succeeded, with a message main() should return report_errors() I gather this error is emitted by the Boost.Lightweight_test library whenever a test's main() function does not call `report_errors()` at the end. The problem in my case is that my failing tests are not (explicitly) using Boost.Lightweight_test. In fact, in all of the failing cases I'm not even writing a `main()` function, as the test driver is a Python script that's importing a (test) module. For example: https://www.boost.org/development/tests/master/developer/output/teeks99-05-m... Does anyone understand or has an idea how this could happen, and how to fix this ? Thanks, Stefan -- ...ich hab' noch einen Koffer in Berlin...
stefan wrote:
Hello,
With the Boost.Python tests I'm observing a couple of mysterious failures, where the test application fails *after* the actual test succeeded, with a message
main() should return report_errors()
I gather this error is emitted by the Boost.Lightweight_test library whenever a test's main() function does not call `report_errors()` at the end. The problem in my case is that my failing tests are not (explicitly) using Boost.Lightweight_test. In fact, in all of the failing cases I'm not even writing a `main()` function, as the test driver is a Python script that's importing a (test) module.
For example: https://www.boost.org/development/tests/master/developer/output/teeks99-05-m...
Looks like this ought to have been fixed by https://github.com/boostorg/python/pull/259/files. A search for lightweight_test in boostorg/python turns up nothing else suspicious. This commit, along with all the others since April, hasn't been merged to master though, and is consequently not in 1.74.
On 2020-08-14 10:10 a.m., Peter Dimov via Boost wrote:
stefan wrote:
Hello,
With the Boost.Python tests I'm observing a couple of mysterious failures, where the test application fails *after* the actual test succeeded, with a message
main() should return report_errors()
I gather this error is emitted by the Boost.Lightweight_test library whenever a test's main() function does not call `report_errors()` at the end. The problem in my case is that my failing tests are not (explicitly) using Boost.Lightweight_test. In fact, in all of the failing cases I'm not even writing a `main()` function, as the test driver is a Python script that's importing a (test) module.
For example: https://www.boost.org/development/tests/master/developer/output/teeks99-05-m...
Looks like this ought to have been fixed by https://github.com/boostorg/python/pull/259/files. A search for lightweight_test in boostorg/python turns up nothing else suspicious.
Oh, you are right ! I was looking at the test report from master, but was looking at the code from the `development` branch.
This commit, along with all the others since April, hasn't been merged to master though, and is consequently not in 1.74.
Yes, sorry about that. I'm now trying to catch up on a number of issues - unfortunately too late for 1.74, but will make sure to merge all the current work as soon as the release is done. Stefan -- ...ich hab' noch einen Koffer in Berlin...
participants (2)
-
Peter Dimov -
stefan