Re: [PATCH 3/3] gitlab: use 'setarch -R' to workaround tsan bug

2024-05-13 Thread Daniel P . Berrangé
On Mon, May 13, 2024 at 12:15:51PM +0100, Daniel P. Berrangé wrote: > The TSAN job started failing when gitlab rolled out their latest > release. The root cause is a change in the Google COS version used > on shared runners. This brings a kernel running with > > vm.mmap_rnd_bits = 31 > > which

Re: [PATCH 3/3] gitlab: use 'setarch -R' to workaround tsan bug

2024-05-13 Thread Thomas Huth
On 13/05/2024 13.15, Daniel P. Berrangé wrote: The TSAN job started failing when gitlab rolled out their latest release. The root cause is a change in the Google COS version used on shared runners. This brings a kernel running with vm.mmap_rnd_bits = 31 which is incompatible with TSAN in

[PATCH 3/3] gitlab: use 'setarch -R' to workaround tsan bug

2024-05-13 Thread Daniel P . Berrangé
The TSAN job started failing when gitlab rolled out their latest release. The root cause is a change in the Google COS version used on shared runners. This brings a kernel running with vm.mmap_rnd_bits = 31 which is incompatible with TSAN in LLVM < 18, which only supports upto '28'. LLVM 18 can