Link boost stacktrace appropriately for line information. #2617
Triggered via pull request
January 28, 2025 15:55
pwojcikdev
Status
Failure
Total duration
1h 17m 4s
Artifacts
–
code_sanitizers.yml
on: pull_request
Matrix: linux_sanitizers
Matrix: macos_sanitizers
Annotations
27 errors
|
macOS [TSAN] [lmdb | clang]
unable to access 'https://github.com/boostorg/move.git/': Failed to connect to github.com port 443 after 75005 ms: Couldn't connect to server
|
|
macOS [TSAN] [lmdb | clang]
Fetched in submodule path 'submodules/boost/libs/move', but it did not contain 70c57e804f6c287c0ee3ab39c2ef1bb9ec9c02e5. Direct fetching of that commit failed.
|
|
macOS [TSAN] [lmdb | clang]
Failed to recurse into submodule path 'submodules/boost'
|
|
macOS [TSAN] [lmdb | clang]
The process '/opt/homebrew/bin/git' failed with exit code 128
|
|
macOS [UBSAN] [lmdb | clang]
RPC failed; HTTP 404 curl 22 The requested URL returned error: 404
|
|
macOS [UBSAN] [lmdb | clang]
expected 'acknowledgments'
|
|
macOS [UBSAN] [lmdb | clang]
Fetched in submodule path 'submodules/boost/libs/tokenizer', but it did not contain 90106f155bd72b62aaca0d9ad826f4132030dba0. Direct fetching of that commit failed.
|
|
macOS [UBSAN] [lmdb | clang]
Failed to recurse into submodule path 'submodules/boost'
|
|
macOS [UBSAN] [lmdb | clang]
The process '/opt/homebrew/bin/git' failed with exit code 128
|
|
Linux [ASAN_INT] [lmdb | clang] (Errors Ignored)
Issues were reported in the sanitizer report.
|
|
Linux [ASAN_INT] [lmdb | clang] (Errors Ignored)
Process completed with exit code 1.
|
|
Linux [ASAN_INT] [lmdb | clang] (Errors Ignored)
Test failed: core_test
|
|
Linux [ASAN_INT] [lmdb | clang] (Errors Ignored)
Process completed with exit code 134.
|
|
Linux [UBSAN] [lmdb | clang]
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Linux [UBSAN] [lmdb | clang]
Process completed with exit code 143.
|
|
Linux [LEAK] [lmdb | clang]
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Linux [LEAK] [lmdb | clang]
The operation was canceled.
|
|
Linux [ASAN] [lmdb | clang]
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Linux [ASAN] [lmdb | clang]
The operation was canceled.
|
|
Linux [ASAN_INT] [rocksdb | clang] (Errors Ignored)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Linux [ASAN_INT] [rocksdb | clang] (Errors Ignored)
Process completed with exit code 143.
|
|
Linux [ASAN] [rocksdb | clang]
Test failed: core_test
|
|
Linux [ASAN] [rocksdb | clang]
Process completed with exit code 134.
|
|
Linux [TSAN] [lmdb | clang]
The hosted runner: GitHub Actions 29 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Linux [LEAK] [rocksdb | clang]
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Linux [LEAK] [rocksdb | clang]
Process completed with exit code 143.
|
|
Linux [UBSAN] [rocksdb | clang]
The hosted runner: GitHub Actions 20 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|