my tester on the release branch failed tonight with: # Running Boost.Build tests Traceback (most recent call last): File "run.py", line 60, in <module> runner(root) File "/home/michael/boost_testing_release/tools_regression_src/regression.py", line 205, in __init__ self.main() File "/home/michael/boost_testing_release/tools_regression_src/regression.py", line 566, in main getattr(self,action_m)() File "/home/michael/boost_testing_release/tools_regression_src/regression.py", line 531, in command_regression self.command_test() File "/home/michael/boost_testing_release/tools_regression_src/regression.py", line 329, in command_test self.command_test_boost_build() File "/home/michael/boost_testing_release/tools_regression_src/regression.py", line 369, in command_test_boost_build "boost/bin.v2/libs/any/test/any_test.test")); OSError: [Errno 2] No such file or directory: '/home/michael/boost_testing_release/results/boost/bin.v2/libs/any/test/any_test.test' On Sun, Sep 29, 2013 at 8:24 AM, Antony Polukhin <antoshkka@gmail.com>wrote:
2013/9/29 Andrey Semashev <andrey.semashev@gmail.com>
On 28 September 2013 21:05, Rene Rivera <grafikrobot@gmail.com> wrote:
As of few minutes ago I was getting a missing target in the variant
Which I have commented out so that testing can progress. Hopefully
On Sunday 29 September 2013 13:33:52 Daniel James wrote: lib. that's
enough to repair the stalled testing.
This kind of thing happens a lot. Would it be possible for the test toolset to check for missing files and report a failed test rather than breaking the whole build?
I think, a more general solution would be to do this for any targets, not just tests.
I like that idea. It would be also great if incorrect format of explicit-failures-markup.xml file won't be treated as fatal error, but rather the whole explicit-failures-markup.xml file would be ignored.
-- Best regards, Antony Polukhin
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost