`HwyBlockwiseShiftTest.TestAllShiftRightLanes` test failing on Graviton3

I'm trying to compile Highway 1.0.3 with [EasyBuild](https://easybuild.io) using the following recipe: https://github.com/easybuilders/easybuild-easyconfigs/blob/develop/easybuild/easyconfigs/h/Highway/Highway-1.0.3-GCCcore-12.2.0.eb.
The build completes without any issues, but one test is failing:
```
211/658 Test #211: HwyBlockwiseShiftTestGroup/HwyBlockwiseShiftTest.TestAllShiftRightLanes/SVE_256 # GetParam() = 33554432 ...............Subprocess aborted***Exception: 0.55 sec
Running main() from /tmp/bot/easybuild/build/googletest/1.12.1/GCCcore-12.2.0/googletest-release-1.12.1/googletest/src/gtest_main.cc
Note: Google Test filter = HwyBlockwiseShiftTestGroup/HwyBlockwiseShiftTest.TestAllShiftRightLanes/SVE_256
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from HwyBlockwiseShiftTestGroup/HwyBlockwiseShiftTest
[ RUN ] HwyBlockwiseShiftTestGroup/HwyBlockwiseShiftTest.TestAllShiftRightLanes/SVE_256

i32x8 expect [2+ ->]:
4,0,0,7,8,0,
i32x8 actual [2+ ->]:
4,0,6,7,8,0,
Abort at /tmp/bot/easybuild/build/Highway/1.0.3/GCCcore-12.2.0/highway-1.0.3/hwy/tests/blockwise_shift_test.cc:135: SVE_256, i32x8 lane 4 mismatch: expected '0', got '6'.
```

This is on a `c7g.4xlarge` instance in AWS, and this is the `lscpu` output:
```
$ lscpu
Architecture: aarch64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 16
On-line CPU(s) list: 0-15
Vendor ID: ARM
Model name: Neoverse-V1
Model: 1
Thread(s) per core: 1
Core(s) per socket: 16
Socket(s): 1
Stepping: r1p1
BogoMIPS: 2100.00
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asim
ddp sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs dcpodp svei8mm svebf16 i8mm bf16 dgh rng
Caches (sum of all):
L1d: 1 MiB (16 instances)
L1i: 1 MiB (16 instances)
L2: 16 MiB (16 instances)
L3: 32 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-15
Vulnerabilities:
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Retbleed: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1: Mitigation; __user pointer sanitization
Spectre v2: Mitigation; CSV2, BHB
Srbds: Not affected
Tsx async abort: Not affected
```

Any idea why this test is failing?