Closed pdimov closed 6 years ago
Looks like the Intrusive library is not updated for these tests. Boost.Container is using a macro from Boost.Intrusive that is not present in the tested version. Maybe the superproject is not updated?
Yes, that's it. You've updated both intrusive and container at the same time, and the bot has updated container first in https://github.com/boostorg/boost/commit/69685c28acd193d7a041e5570bdf6151dd2962c3, then intrusive in https://github.com/boostorg/boost/commit/89050221222049a1dc00f239090f43f53f94ccf1. False alarm.
From https://travis-ci.org/boostorg/boost/jobs/295693904 and https://ci.appveyor.com/project/boostorg/boost/build/1.0.4464-master/job/mhcujct9n5lj4fdg.
I can't reproduce this locally, so it might have been caused by a temporarily broken Interprocess.
I'm enabling some minimal Travis here, to get some CI.