Re: Boost.Compute broken in 1.86.0 because of UUID changes, 1.86.1?

From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2024-08-22 10:57:39

On 8/22/24 12:54, Peter Dimov via Boost wrote:
> Boris Kolpackov wrote:
>> Peter Dimov via Boost <boost_at_[hidden]> writes:
>>
>>> Because Boost.Compute (boost/compute/detail/sha1.hpp) uses an
>>> implementation detail of Boost.UUID (boost/uuid/detail/sha1.hpp), and
>>> because I changed the implementation to fix an endianness issue,
>>> <boost/compute.hpp> now causes a compile error in 1.86.0
>>
>> Any sense why this was not detected (e.g., by CI) when the change was made
>> or during pre-release testing? It seems to me compiling any translation unit
>> that included <boost/compute.hpp> would have picked this up, no?
> 
> It would have, but no such translation unit was compiled by anyone before
> the release went out.

CI gets run when a tag is pushed, so 1.86.0 beta1 should have triggered
the CI. The problem is that there was noone to notice its failure.