2014-06-23 13:53 GMT+02:00 Andrey Semashev
2014-06-23 11:40 GMT+02:00 Andrey Semashev
: On Monday 23 June 2014 09:46:56 Andrzej Krzemienski wrote:
Hi, Recently I observed lots of test cases showing as failed in regression tests on branch 'develop' in Boost.Optional:
http://www.boost.org/development/tests/develop/developer/optional.html
When I try to inspect the results they are either empty or refer to
places in the code that do not exist anymore in branch 'develop', as
though
the test environments were using partial results of GIT commits. But
On Monday 23 June 2014 12:32:31 Andrzej Krzemienski wrote: the the
test dates are after the last commit, so it looks like something is
broken
with the testing framework. Anyone can help me with figuring out what to do?
Which tests do you mean?
This one, for instance:
http://www.boost.org/development/tests/develop/developer/output/teeks99-03e-> Ubuntu12-04-64-boost-bin-v2-libs-optional-test-optional_test_value_access-te
st-gcc-4-8-debug.html
The error message quotes a piece of implementation:
value_or ( U const& v ) const { return this->is_initialized() ? get() : (v); }
But there exists no such code in the current implementation in branch 'develop'. I am using no ternary operators (I used to in the previous commits). The test's date is that of today. My last commit was on Friday.
Yes, looks like a problem. Maybe the checkout failed at some point for the tester, and Boost.Optional submodule was left in outdated state. I sometimes get timeouts from GitHub when I update Boost tree, I think in such cases the tree is left in some semi-updated state; I didn't check though. If the update scripts ignore such errors then that's what may have happened.
What's the procedure in such cases? Can the owners of the machines/environments /scripts be contacted? regards, &rzej