Skip to content

fix: Failing install script #87

fix: Failing install script

fix: Failing install script #87

Triggered via pull request September 4, 2025 11:59
Status Failure
Total duration 7m 12s
Artifacts –

ci.yml

on: pull_request
Matrix: job_compile
Build Package
27s
Build Package
Matrix: job_test_bindings
All required jobs passed
4s
All required jobs passed
Fit to window
Zoom out
Zoom in

Annotations

21 errors and 4 notices
Compile Binary (v18) ubuntu-22.04, ghcr.io/getsentry/sentry-test-ubuntu-20.04-amd64:0dd255f3d41d013c1db4c4e08ffd22ee7959c3cc, glibc
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Compile Binary (v18) ubuntu-22.04, ghcr.io/getsentry/sentry-test-ubuntu-20.04-amd64:0dd255f3d41d013c1db4c4e08ffd22ee7959c3cc, glibc
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Compile Binary (v18) ubuntu-22.04, ghcr.io/getsentry/sentry-test-ubuntu-20.04-amd64:0dd255f3d41d013c1db4c4e08ffd22ee7959c3cc, glibc
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Compile Binary (v20) ubuntu-22.04, ghcr.io/getsentry/sentry-test-ubuntu-20.04-amd64:0dd255f3d41d013c1db4c4e08ffd22ee7959c3cc, glibc
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Compile Binary (v20) ubuntu-22.04, ghcr.io/getsentry/sentry-test-ubuntu-20.04-amd64:0dd255f3d41d013c1db4c4e08ffd22ee7959c3cc, glibc
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Compile Binary (v20) ubuntu-22.04, ghcr.io/getsentry/sentry-test-ubuntu-20.04-amd64:0dd255f3d41d013c1db4c4e08ffd22ee7959c3cc, glibc
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Compile Binary (v22) ubuntu-22.04, ghcr.io/getsentry/sentry-test-ubuntu-20.04-amd64:0dd255f3d41d013c1db4c4e08ffd22ee7959c3cc, glibc
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Compile Binary (v22) ubuntu-22.04, ghcr.io/getsentry/sentry-test-ubuntu-20.04-amd64:0dd255f3d41d013c1db4c4e08ffd22ee7959c3cc, glibc
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Compile Binary (v22) ubuntu-22.04, ghcr.io/getsentry/sentry-test-ubuntu-20.04-amd64:0dd255f3d41d013c1db4c4e08ffd22ee7959c3cc, glibc
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Compile Binary (v24) ubuntu-22.04, ghcr.io/getsentry/sentry-test-ubuntu-20.04-amd64:0dd255f3d41d013c1db4c4e08ffd22ee7959c3cc, glibc
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Compile Binary (v24) ubuntu-22.04, ghcr.io/getsentry/sentry-test-ubuntu-20.04-amd64:0dd255f3d41d013c1db4c4e08ffd22ee7959c3cc, glibc
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Compile Binary (v24) ubuntu-22.04, ghcr.io/getsentry/sentry-test-ubuntu-20.04-amd64:0dd255f3d41d013c1db4c4e08ffd22ee7959c3cc, glibc
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Test (v18) ubuntu-24.04
Process completed with exit code 1.
Test (v18) macos-latest
Process completed with exit code 1.
Test (v18) ubuntu-22.04
Process completed with exit code 1.
Test (v18) ubuntu-22.04-arm
Process completed with exit code 1.
Test (v18) macos-13
Process completed with exit code 1.
Test (v24) macos-latest
Process completed with exit code 1.
test/e2e.test.mjs > e2e Tests > Capture stack trace from multiple threads: test/e2e.test.mjs#L16
AssertionError: expected [ { function: '?', …(3) } ] to deeply equal ArrayContaining{…} - Expected + Received - ArrayContaining [ + [ { - "colno": Any<Number>, - "filename": Any<String>, - "function": "pbkdf2Sync", - "lineno": Any<Number>, - }, - { - "colno": Any<Number>, - "filename": StringMatching /long-work.js$/, - "function": "longWork", - "lineno": Any<Number>, - }, - { - "colno": Any<Number>, - "filename": StringMatching /stack-traces.js$/, + "colno": 31, + "filename": "node:internal/per_context/messageport", "function": "?", - "lineno": Any<Number>, + "lineno": 19, }, ] ❯ test/e2e.test.mjs:16:32
Test (v18) windows-latest
Process completed with exit code 1.
All required jobs passed
Process completed with exit code 1.
Test (v18) windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test (v24) windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test (v22) windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Test (v20) windows-latest
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677