On Wed, Sep 27, 2023 at 6:06 PM Peter Dimov via Boost
Tom Kent wrote:
Starting sometime between 3am and 5pm on September 11, 2023, all the windows regression runners started failing on the develop branch.
Master branch runners on the same VM are still doing fine ( https://www.boost.org/development/tests/master/developer/summary.html) .
The output doesn't have anything jump out at me. Nor were there any commits to the develop branch in that window that seem suspicious to me.
The regression run output ends with: ...found 1 target...
[...]
With the full output available here: https://gist.github.com/teeks99/bb4230f6a1efdd7af11bd93341c950bf
Any ideas on this would be much appreciated.
According to the log, the script tries to build process_jam_log.exe using msvc-10.0.
Since process_jam_log depends on Boost.Filesystem, which now requires C++11, the build silently fails.
Any ideas on how I can convince that build to use msvc-14.3 while keeping msvc-10.0 in my user-config.jam? I'm guessing there is some auto-picking logic at play that I might be able to control? I'd like to keep still testing with that version of visual studio a bit longer, thus I don't want to completely get rid of it. Thanks, Tom