Since the issue is caused by an undefined behavior optimization, possibly the tests ran on a different optimization level or on a different architecture target?

Since the issue is caused by an undefined behavior optimization, possibly the tests ran on a different optimization level or on a different architecture target? Would still be surprising, but less so than there not being tests at all.