On Monday 23 June 2014 13:57:50 Andrzej Krzemienski wrote:
2014-06-23 13:53 GMT+02:00 Andrey Semashev
: 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?
Yes, if the contact information is available in the tester description (the link in the test results table header). E.g. for your tester the information is: http://www.boost.org/development/tests/develop/teeks99-03e-Ubuntu12-04-64.ht... Tom is usually reading this list, I hope he's reading this.