-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
roachtest: acceptance/version-upgrade failed: workload crashes with Illegal instruction #58754
Comments
(roachtest).acceptance/version-upgrade failed on release-20.1@5197d58536a02e2f9170aee340dc1a70c87ead7a:
More
Artifacts: /acceptance/version-upgrade
See this test on roachdash |
I've been trying to reproduce, no luck so far. |
(roachtest).acceptance/version-upgrade failed on release-20.1@217be74f52b63537110775d79a423a27cfa06c4d:
More
Artifacts: /acceptance/version-upgrade
See this test on roachdash |
Started a run with debug=on: https://teamcity.cockroachdb.com/viewLog.html?buildId=2582001& This is what I get on one left over hosts with
|
Line of code:
Offending instruction:
|
vpxord is part of the AVX512 instruction set. Very surprising that this is used by default.. Maybe we want to pass |
Or perhaps
|
I think the problem is this line in
I noticed some |
(roachtest).acceptance/version-upgrade failed on release-20.1@217be74f52b63537110775d79a423a27cfa06c4d:
More
Artifacts: /acceptance/version-upgrade
See this test on roachdash |
When building release binaries, we pass |
Something recently changed on the TC agents (presumably usage of a new machine type with a different CPU) so that using `-march=native` when building RocksDB causes AVX512 instructions to be used which are not present on roachprod machines. The result is that binaries built in this way will die with "illegal instruction". RocksDB has a mechanism to disable the use of `-march=native`: pass `PORTABLE=1` to the make command. We were already doing this for release builds. Now we're doing it for all builds. Fixes cockroachdb#58754 Release note: none
Something recently changed on the TC agents (presumably usage of a new machine type with a different CPU) so that using `-march=native` when building RocksDB causes AVX512 instructions to be used which are not present on roachprod machines. The result is that binaries built in this way will die with "illegal instruction". RocksDB has a mechanism to disable the use of `-march=native`: pass `PORTABLE=1` to the make command. We were already doing this for release builds. Now we're doing it for all builds. Fixes cockroachdb#58754 Release note: none
#58997 fixed this, this test passed in https://teamcity.cockroachdb.com/viewLog.html?buildId=2584467& |
Something recently changed on the TC agents (presumably usage of a new machine type with a different CPU) so that using `-march=native` when building RocksDB causes AVX512 instructions to be used which are not present on roachprod machines. The result is that binaries built in this way will die with "illegal instruction". RocksDB has a mechanism to disable the use of `-march=native`: pass `PORTABLE=1` to the make command. We were already doing this for release builds. Now we're doing it for all builds. Fixes cockroachdb#58754 Release note: none
Something recently changed on the TC agents (presumably usage of a new machine type with a different CPU) so that using `-march=native` when building RocksDB causes AVX512 instructions to be used which are not present on roachprod machines. The result is that binaries built in this way will die with "illegal instruction". RocksDB has a mechanism to disable the use of `-march=native`: pass `PORTABLE=1` to the make command. We were already doing this for release builds. Now we're doing it for all builds. Fixes #58754 Release note: none
(roachtest).acceptance/version-upgrade failed on release-20.1@e395c0c7c48a279334f0e94dfb7030a3eafa093f:
More
Artifacts: /acceptance/version-upgrade
Related:
roachtest: schemaChangeStep is skipped in acceptance/version-upgrade #58489 roachtest: acceptance/version-upgrade failed C-test-failure O-roachtest O-robot branch-master release-blocker
roachtest: acceptance/version-upgrade failed #58329 roachtest: acceptance/version-upgrade failed C-test-failure O-roachtest O-robot branch-release-note-script-update release-blocker
roachtest: acceptance/version-upgrade failed: invalid attempted write of database descriptor #58307 roachtest: acceptance/version-upgrade failed A-schema-descriptors C-bug C-test-failure O-roachtest branch-release-20.2
roachtest: acceptance/version-upgrade failed #53812 roachtest: acceptance/version-upgrade failed C-test-failure O-roachtest O-robot branch-release-19.2
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: