Modify boringssl to run nplb #18877
Triggered via pull request
February 24, 2025 23:17
Status
Failure
Total duration
20m 46s
Artifacts
–
linux.yaml
on: pull_request
chromium_linux-x64
/
initialize
1m 12s
linux-evergreen
/
initialize
1m 13s
linux
/
initialize
1m 8s
Matrix: chromium_linux-x64 / build
Matrix: linux-evergreen / build
Matrix: linux / build
Matrix: chromium_linux-x64 / on-device-test
Matrix: chromium_linux-x64 / on-host-test
Matrix: linux-evergreen / on-device-test
Matrix: linux-evergreen / on-host-test
Matrix: linux / on-device-test
Matrix: linux / on-host-test
Matrix: chromium_linux-x64 / test-results
Waiting for pending jobs
Matrix: linux-evergreen / test-results
Matrix: linux / test-results
Matrix: chromium_linux-x64 / validate-test-result
Matrix: linux-evergreen / validate-test-result
Matrix: linux / validate-test-result
Annotations
156 errors and 3 warnings
linux-evergreen / x64_devel
Process completed with exit code 1.
|
linux-evergreen / x64_gold
Process completed with exit code 1.
|
linux-evergreen / x64_qa
Process completed with exit code 1.
|
chromium_linux-x64 / x64_qa
Canceling since a higher priority waiting request for 'linux-chromium_linux @ modify_boringssl' exists
|
chromium_linux-x64 / x64_devel
Canceling since a higher priority waiting request for 'linux-chromium_linux @ modify_boringssl' exists
|
linux / x64_devel
Canceling since a higher priority waiting request for 'linux-linux @ modify_boringssl' exists
|
chromium_linux-x64 / x64_gold
Canceling since a higher priority waiting request for 'linux-chromium_linux @ modify_boringssl' exists
|
linux / x64_gold
Canceling since a higher priority waiting request for 'linux-linux @ modify_boringssl' exists
|
linux / x64_qa
Canceling since a higher priority waiting request for 'linux-linux @ modify_boringssl' exists
|
chromium_linux-x64 / x64_tests_passing
Process completed with exit code 1.
|
linux / x64_on_host_tests_4
Unable to download artifact(s): Artifact not found for name: linux-x64x11_x64_test_artifacts
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
linux / x64_on_host_tests_4
EPERM: operation not permitted, stat '/proc/1/map_files/577c0b3ad000-577c0b3af000'
|
linux / x64_on_host_tests_6
Unable to download artifact(s): Artifact not found for name: linux-x64x11_x64_test_artifacts
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
linux / x64_on_host_tests_6
EPERM: operation not permitted, stat '/proc/1/map_files/5b8385c06000-5b8385c08000'
|
linux / x64_on_host_tests_0
Unable to download artifact(s): Artifact not found for name: linux-x64x11_x64_test_artifacts
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
linux / x64_on_host_tests_0
EPERM: operation not permitted, stat '/proc/1/map_files/598d5f2ce000-598d5f2d0000'
|
linux / x64_on_host_tests_9
Unable to download artifact(s): Artifact not found for name: linux-x64x11_x64_test_artifacts
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
linux / x64_on_host_tests_9
EPERM: operation not permitted, stat '/proc/1/map_files/5a1be43ae000-5a1be43b0000'
|
linux / x64_on_host_tests_5
Unable to download artifact(s): Artifact not found for name: linux-x64x11_x64_test_artifacts
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
linux / x64_on_host_tests_5
EPERM: operation not permitted, stat '/proc/1/map_files/5a1af90c7000-5a1af90c9000'
|
linux / x64_on_host_tests_8
Unable to download artifact(s): Artifact not found for name: linux-x64x11_x64_test_artifacts
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
linux / x64_on_host_tests_8
EPERM: operation not permitted, stat '/proc/1/map_files/5abdce419000-5abdce41b000'
|
linux / x64_on_host_tests_7
Unable to download artifact(s): Artifact not found for name: linux-x64x11_x64_test_artifacts
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
linux / x64_on_host_tests_7
EPERM: operation not permitted, stat '/proc/1/map_files/5a697c203000-5a697c205000'
|
linux / x64_on_host_tests_1
Unable to download artifact(s): Artifact not found for name: linux-x64x11_x64_test_artifacts
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
linux / x64_on_host_tests_1
EPERM: operation not permitted, stat '/proc/1/map_files/5d1971ce7000-5d1971ce9000'
|
linux / x64_on_host_tests_2
Unable to download artifact(s): Artifact not found for name: linux-x64x11_x64_test_artifacts
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
linux / x64_on_host_tests_2
EPERM: operation not permitted, stat '/proc/1/map_files/593cc3e9f000-593cc3ea1000'
|
linux / x64_on_host_tests_3
Unable to download artifact(s): Artifact not found for name: linux-x64x11_x64_test_artifacts
Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact.
For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
|
linux / x64_on_host_tests_3
EPERM: operation not permitted, stat '/proc/1/map_files/55593b1cb000-55593b1cd000'
|
linux / cc:cc_unittests
No test results found. Did the test crash?
|
linux / cc:cc_unittests
Process completed with exit code 1.
|
linux / cc:cc_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / cc:cc_unittests
Process completed with exit code 1.
|
linux / crypto:crypto_unittests
No test results found. Did the test crash?
|
linux / crypto:crypto_unittests
Process completed with exit code 1.
|
linux / crypto:crypto_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / crypto:crypto_unittests
Process completed with exit code 1.
|
linux / base:base_unittests
No test results found. Did the test crash?
|
linux / base:base_unittests
Process completed with exit code 1.
|
linux / base:base_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / base:base_unittests
Process completed with exit code 1.
|
linux / ui/ozone:ozone_unittests
No test results found. Did the test crash?
|
linux / ui/ozone:ozone_unittests
Process completed with exit code 1.
|
linux / ui/ozone:ozone_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / ui/ozone:ozone_unittests
Process completed with exit code 1.
|
linux / device:device_unittests
No test results found. Did the test crash?
|
linux / device:device_unittests
Process completed with exit code 1.
|
linux / device:device_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / device:device_unittests
Process completed with exit code 1.
|
linux / media/capture:capture_unittests
No test results found. Did the test crash?
|
linux / media/capture:capture_unittests
Process completed with exit code 1.
|
linux / media/capture:capture_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / media/capture:capture_unittests
Process completed with exit code 1.
|
linux / components/viz:viz_perftests
No test results found. Did the test crash?
|
linux / components/viz:viz_perftests
Process completed with exit code 1.
|
linux / components/viz:viz_perftests
No test logs found. Check device lab logs to see what went wrong.
|
linux / components/viz:viz_perftests
Process completed with exit code 1.
|
linux / components/viz:viz_unittests
No test results found. Did the test crash?
|
linux / components/viz:viz_unittests
Process completed with exit code 1.
|
linux / url:url_perftests
No test results found. Did the test crash?
|
linux / components/viz:viz_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / url:url_perftests
Process completed with exit code 1.
|
linux / components/viz:viz_unittests
Process completed with exit code 1.
|
linux / url:url_perftests
No test logs found. Check device lab logs to see what went wrong.
|
linux / url:url_perftests
Process completed with exit code 1.
|
linux / cobalt:cobalt_unittests
No test results found. Did the test crash?
|
linux / cobalt:cobalt_unittests
Process completed with exit code 1.
|
linux / cobalt:cobalt_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / cobalt:cobalt_unittests
Process completed with exit code 1.
|
linux / ppapi:ppapi_perftests
No test results found. Did the test crash?
|
linux / ppapi:ppapi_perftests
Process completed with exit code 1.
|
linux / ppapi:ppapi_perftests
No test logs found. Check device lab logs to see what went wrong.
|
linux / ppapi:ppapi_perftests
Process completed with exit code 1.
|
linux / services/service_manager/tests:service_manager_unittests
No test results found. Did the test crash?
|
linux / services/service_manager/tests:service_manager_unittests
Process completed with exit code 1.
|
linux / services/service_manager/tests:service_manager_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / services/service_manager/tests:service_manager_unittests
Process completed with exit code 1.
|
linux / ipc:ipc_tests
No test results found. Did the test crash?
|
linux / sql:sql_unittests
No test results found. Did the test crash?
|
linux / ipc:ipc_tests
Process completed with exit code 1.
|
linux / sql:sql_unittests
Process completed with exit code 1.
|
linux / ipc:ipc_tests
No test logs found. Check device lab logs to see what went wrong.
|
linux / sql:sql_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / ipc:ipc_tests
Process completed with exit code 1.
|
linux / sql:sql_unittests
Process completed with exit code 1.
|
linux / starboard/nplb:nplb
No test results found. Did the test crash?
|
linux / starboard/nplb:nplb
Process completed with exit code 1.
|
linux / starboard/nplb:nplb
No test logs found. Check device lab logs to see what went wrong.
|
linux / starboard/nplb:nplb
Process completed with exit code 1.
|
linux / ppapi:ppapi_unittests
No test results found. Did the test crash?
|
linux / ppapi:ppapi_unittests
Process completed with exit code 1.
|
linux / ppapi:ppapi_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / ppapi:ppapi_unittests
Process completed with exit code 1.
|
linux / google_apis:google_apis_unittests
No test results found. Did the test crash?
|
linux / google_apis:google_apis_unittests
Process completed with exit code 1.
|
linux / google_apis:google_apis_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / google_apis:google_apis_unittests
Process completed with exit code 1.
|
linux / skia:skia_unittests
No test results found. Did the test crash?
|
linux / skia:skia_unittests
Process completed with exit code 1.
|
linux / skia:skia_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / media/midi:midi_unittests
No test results found. Did the test crash?
|
linux / skia:skia_unittests
Process completed with exit code 1.
|
linux / media/midi:midi_unittests
Process completed with exit code 1.
|
linux / media/midi:midi_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / media/midi:midi_unittests
Process completed with exit code 1.
|
linux / gpu:gpu_unittests
No test results found. Did the test crash?
|
linux / gpu:gpu_unittests
Process completed with exit code 1.
|
linux / gpu:gpu_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / gpu:gpu_benchmark
No test results found. Did the test crash?
|
linux / gpu:gpu_unittests
Process completed with exit code 1.
|
linux / gpu:gpu_benchmark
Process completed with exit code 1.
|
linux / gpu:gpu_benchmark
No test logs found. Check device lab logs to see what went wrong.
|
linux / gpu:gpu_benchmark
Process completed with exit code 1.
|
linux / gpu:command_buffer_perftests
No test results found. Did the test crash?
|
linux / gpu:command_buffer_perftests
Process completed with exit code 1.
|
linux / gpu:command_buffer_perftests
No test logs found. Check device lab logs to see what went wrong.
|
linux / gpu:command_buffer_perftests
Process completed with exit code 1.
|
linux / google_apis/gcm:gcm_unit_tests
No test results found. Did the test crash?
|
linux / google_apis/gcm:gcm_unit_tests
Process completed with exit code 1.
|
linux / google_apis/gcm:gcm_unit_tests
No test logs found. Check device lab logs to see what went wrong.
|
linux / google_apis/gcm:gcm_unit_tests
Process completed with exit code 1.
|
linux / gpu:gl_tests
No test results found. Did the test crash?
|
linux / gpu:gl_tests
Process completed with exit code 1.
|
linux / gpu:gl_tests
No test logs found. Check device lab logs to see what went wrong.
|
linux / gpu:gl_tests
Process completed with exit code 1.
|
linux / ui/wm:wm_unittests
No test results found. Did the test crash?
|
linux / ui/wm:wm_unittests
Process completed with exit code 1.
|
linux / ui/wm:wm_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / ui/wm:wm_unittests
Process completed with exit code 1.
|
linux / media:media_unittests
No test results found. Did the test crash?
|
linux / media:media_unittests
Process completed with exit code 1.
|
linux / media:media_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / media:media_unittests
Process completed with exit code 1.
|
linux / gpu:gpu_perftests
No test results found. Did the test crash?
|
linux / gpu:gpu_perftests
Process completed with exit code 1.
|
linux / gpu:gpu_perftests
No test logs found. Check device lab logs to see what went wrong.
|
linux / gpu:gpu_perftests
Process completed with exit code 1.
|
linux / cc:cc_perftests
No test results found. Did the test crash?
|
linux / cc:cc_perftests
Process completed with exit code 1.
|
linux / cc:cc_perftests
No test logs found. Check device lab logs to see what went wrong.
|
linux / cc:cc_perftests
Process completed with exit code 1.
|
linux / gpu/gles2_conform_support:gles2_conform_test
No test results found. Did the test crash?
|
linux / gpu/gles2_conform_support:gles2_conform_test
Process completed with exit code 1.
|
linux / gpu/gles2_conform_support:gles2_conform_test
No test logs found. Check device lab logs to see what went wrong.
|
linux / gpu/gles2_conform_support:gles2_conform_test
Process completed with exit code 1.
|
linux / mojo:mojo_perftests
No test results found. Did the test crash?
|
linux / mojo:mojo_perftests
Process completed with exit code 1.
|
linux / mojo:mojo_perftests
No test logs found. Check device lab logs to see what went wrong.
|
linux / mojo:mojo_perftests
Process completed with exit code 1.
|
linux / url:url_unittests
No test results found. Did the test crash?
|
linux / url:url_unittests
Process completed with exit code 1.
|
linux / url:url_unittests
No test logs found. Check device lab logs to see what went wrong.
|
linux / url:url_unittests
Process completed with exit code 1.
|
linux / x64_tests_passing
Process completed with exit code 1.
|
linux
Error when evaluating 'strategy' for job 'test-results'. youtube/cobalt/.github/workflows/main.yaml@5e21d86bb6fbf16e837a5146e148a92ee9fe2439 (Line: 300, Col: 22): Error parsing fromJson,youtube/cobalt/.github/workflows/main.yaml@5e21d86bb6fbf16e837a5146e148a92ee9fe2439 (Line: 300, Col: 22): Error reading JToken from JsonReader. Path '', line 0, position 0.,youtube/cobalt/.github/workflows/main.yaml@5e21d86bb6fbf16e837a5146e148a92ee9fe2439 (Line: 300, Col: 22): Unexpected value ''
|
linux-evergreen / docker-build-image
The following actions uses Node.js version which is deprecated and will be forced to run on node20: docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a, isarkis/setup-gcloud@40dce7857b354839efac498d3632050f568090b6. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
chromium_linux-x64 / docker-build-image
The following actions uses Node.js version which is deprecated and will be forced to run on node20: docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a, isarkis/setup-gcloud@40dce7857b354839efac498d3632050f568090b6. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
linux / docker-build-image
The following actions uses Node.js version which is deprecated and will be forced to run on node20: docker/login-action@f4ef78c080cd8ba55a85445d5b36e214a81df20a, isarkis/setup-gcloud@40dce7857b354839efac498d3632050f568090b6. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|