Conversation
|
The model version in the
|
|
🚀 Attempted to deploy 🖥️
|
|
!bump minor |
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
!redeploy |
|
🚀 Attempted to deploy 🖥️
|
|
!redeploy |
|
🚀 Attempted to deploy 🖥️
|
|
!redeploy |
|
🚀 Attempted to deploy 🖥️
|
|
You are getting warnings that indicate the build is using Which is not causing a failure, but this is: It's probably worth specifying |
Interesting, the intel build I tried last night didn't have this issue, but it failed due to the long build time. I'll try gcc now. |
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
minghangli-uni
left a comment
There was a problem hiding this comment.
remove compiler specifier
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
|
🚀 Attempted to deploy 🖥️
|
babeltrace2currently is built targetingx86_64_v4, which enables AVX-512 instructions. This causes an immediateIllegal instructioncrash when importingbt2on Broadwell nodes (e.g. Jupyter sessions on normalbw).One example,
With Jupyter notebook on normalbw (broadwell) queue
While on the login node normal (cascade lake) queue
Since Broadwell is currently the only cpu type used for ARE Jupyter,
babeltrace2should be deployed targetingx86_64[_v3], which should be (?) compatible with Broadwell while remaining fully compatible with normal and normalsr queues.For the vk83 release environment, I've tried
/g/data/vk83/prerelease/apps/spack/0.22/release/linux-rocky8-x86_64_v3, with@gcc-14.1.0/g/data/vk83/prerelease/apps/spack/0.22/release/linux-rocky8-x86_64, with@intel-2021.10.0🚀 The latest prerelease
babeltrace2/pr20-2at 1d49b31 is here: #20 (comment) 🚀🚀 The latest prerelease
babeltrace2/pr20-5at 094941d is here: #20 (comment) 🚀🚀 The latest prerelease
babeltrace2/pr20-15at 6acc9e8 is here: #20 (comment) 🚀