Test issue: legion - Illegal instruction (core dumped) when running run.sh validation test

[SamBosch77]

Summary:
After building spec according to spack.yaml, legion's validation test fails at run time when executing run.sh due to an "Illegal instruction"

Steps to reproduce:

$ ./setup.sh
$ ./clean.sh
$ ./compile.sh
$ ./run.sh

Error output:

sbosch@instinct:~/instinctE4S-22.05/testsuite/validation_tests/legion$ ./run.sh
4sjbscc
g3tu5cd
++ mktemp ./tmp.XXXXXXX
+ TMPFILE=./tmp.3Paqy6j
+ cd build
+ ./legion
./run.sh: line 10: 3983381 Illegal instruction     (core dumped) ./legion > ${TMPFILE}

spack debug report:

• Spack: 0.18.0 (c09bf37ff690c29779a342670cf8a171ad1b9233)
• Python: 3.8.10
• Platform: linux-ubuntu20.04-broadwell
• Concretizer: clingo

Helpful files:
(Changed to .txt extension for upload)
run.sh.txt
spack.yaml.txt

Additional Info:

• Test matches the test from the legion source in legion/tutorial/08_multiple_partitions/multiple_partitions.cc

Package Maintainers and Interested Parties:

• @pmccormick
• @streichler
• @wspear

[eugeneswalker]

Which system is this on? Is this at a facility?

[wspear]

This is on Instinct.

[eugeneswalker]

This is on Instinct.

Has this been observed anywhere else? The deployment of legion, on Instinct, where this is manifesting -- was this deployment performed by actually doing the build on Instinct? Is it possible the legion build was conducted on another machine, but deployed to NFS such that you can access it from Instinct?

[SamBosch77]

In this instance, legion was built with the rest of the environment specs on Instinct specifically. At least, that's what I would assume from initially running spack install while logged in on Instinct. I haven't logged on to any of the other systems while building E4S and validating with the testsuite, so I doubt it would be a NFS issue.