[uss_qualifier/scenarios/utm] Cleanup extents of op intents actually created; Extend max test run duration; Introduce max scenario execution duration for 'Verify clear area' #5085
the-gluci.yml
on: pull_request
Build monitoring image
1m 29s
Repository hygiene
2m 3s
mock_uss tests
/
mock_uss test
58s
uss_qualifier configurations.dev.noop tests
/
uss_qualifier-noop-test test
2m 0s
uss_qualifier configurations.dev.geoawareness_cis tests
/
uss_qualifier-geoawareness_cis-test test
1m 59s
uss_qualifier configurations.dev.generate_rid_test_data tests
/
uss_qualifier-generate_rid_test_data-test test
1m 48s
uss_qualifier configurations.dev.geospatial_comprehension tests
/
uss_qualifier-geospatial_comprehension-test test
1m 52s
uss_qualifier configurations.dev.general_flight_auth tests
/
uss_qualifier-general_flight_auth-test test
1m 56s
uss_qualifier configurations.dev.message_signing tests
/
uss_qualifier-message_signing-test test
2m 39s
uss_qualifier configurations.dev.dss_probing tests
/
uss_qualifier-dss_probing-test test
4m 41s
uss_qualifier configurations.dev.f3548_self_contained tests
/
uss_qualifier-f3548_self_contained-test test
3m 27s
uss_qualifier configurations.dev.utm_implementation_us tests
/
uss_qualifier-utm_implementation_us-test test
3m 20s
uss_qualifier configurations.dev.netrid_v22a tests
/
uss_qualifier-netrid_v22a-test test
9m 0s
uss_qualifier configurations.dev.netrid_v19 tests
/
uss_qualifier-netrid_v19-test test
8m 48s
uss_qualifier configurations.dev.uspace tests
/
uss_qualifier-uspace-test test
3m 31s
prober tests
/
prober test
1m 41s
Unit tests
3m 21s
uss_qualifier configurations.dev.minimal_probing tests
/
uss_qualifier-minimal_probing-test test
2m 17s
Publish GitHub Pages
18s
Annotations
3 errors and 19 warnings
|
uss_qualifier configurations.dev.utm_implementation_us tests / uss_qualifier-utm_implementation_us-test test
Process completed with exit code 2.
|
|
uss_qualifier configurations.dev.f3548_self_contained tests / uss_qualifier-f3548_self_contained-test test
Process completed with exit code 2.
|
|
uss_qualifier configurations.dev.uspace tests / uss_qualifier-uspace-test test
Process completed with exit code 2.
|
|
mock_uss tests / mock_uss test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
mock_uss tests / mock_uss test
No files were found with the provided path: monitoring/uss_qualifier/output
monitoring/prober/output. No artifacts will be uploaded.
|
|
mock_uss tests / mock_uss test
No files were found with the provided path: logs
monitoring/mock_uss/output. No artifacts will be uploaded.
|
|
prober tests / prober test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.generate_rid_test_data tests / uss_qualifier-generate_rid_test_data-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.geospatial_comprehension tests / uss_qualifier-geospatial_comprehension-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.general_flight_auth tests / uss_qualifier-general_flight_auth-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.geoawareness_cis tests / uss_qualifier-geoawareness_cis-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.noop tests / uss_qualifier-noop-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Repository hygiene
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.minimal_probing tests / uss_qualifier-minimal_probing-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.message_signing tests / uss_qualifier-message_signing-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.utm_implementation_us tests / uss_qualifier-utm_implementation_us-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.f3548_self_contained tests / uss_qualifier-f3548_self_contained-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.uspace tests / uss_qualifier-uspace-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.dss_probing tests / uss_qualifier-dss_probing-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.netrid_v19 tests / uss_qualifier-netrid_v19-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
uss_qualifier configurations.dev.netrid_v22a tests / uss_qualifier-netrid_v22a-test test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
monitoring-docker-image
|
376 MB |
sha256:c4c0ab8a72eb83da83f45743d5ce597385c06ef0146d91004547b7dbd0c75da5
|
|
|
monitoring-test-prober-logs
|
111 KB |
sha256:2874bf91f8c6eb0ddb777760133d06d61e1bd10cd5db85875275a67a6a312f58
|
|
|
monitoring-test-prober-reports
|
1.99 KB |
sha256:a2c52b0acc2e5e5adb020db3dbe8674d383d215d013a6ad7afe4e4a385ccce20
|
|
|
monitoring-test-uss_qualifier-dss_probing-test-logs
|
400 KB |
sha256:335bdcc1e96d0d1d202cafab6f29f7fce77d20b83e91623aac98acac5c302031
|
|
|
monitoring-test-uss_qualifier-dss_probing-test-reports
|
1.8 MB |
sha256:35d4461858b60dc8f644a5efc2dc07d5a1b33eae9e917c49dd5e17970fa5cd55
|
|
|
monitoring-test-uss_qualifier-f3548_self_contained-test-logs
|
599 KB |
sha256:054b5244fb3d191098f85dc68faa83dc465922d39e7fc5cd9d574df43db67e99
|
|
|
monitoring-test-uss_qualifier-f3548_self_contained-test-reports
|
1.6 MB |
sha256:a7bf80324a958f5350647aa12c8919b47e7129d08aa8f13e25148d6642d0777d
|
|
|
monitoring-test-uss_qualifier-general_flight_auth-test-logs
|
31.8 KB |
sha256:1fc80afa320180c6f2f70029a6576e2ffcfb2a13bb2305b50680bea028daf5be
|
|
|
monitoring-test-uss_qualifier-general_flight_auth-test-reports
|
23.5 KB |
sha256:9722b361893eef6f59d90c9f5c541fe6d69740f963ea557ee66b577cbafb168c
|
|
|
monitoring-test-uss_qualifier-generate_rid_test_data-test-logs
|
17.8 KB |
sha256:32acc72a70675c94566d9d7d66909a312ada6cefc0751f87b7f03b27b031a71c
|
|
|
monitoring-test-uss_qualifier-generate_rid_test_data-test-reports
|
58.6 KB |
sha256:2a69311cc406fbbfa075fb16c985a40c75eba028ca07272332c431e3f3982fca
|
|
|
monitoring-test-uss_qualifier-geoawareness_cis-test-logs
|
17.8 KB |
sha256:c184f94f2f5951a37e5bce923d623f04d707dcc17f9e15aff95e93ccb4b1de73
|
|
|
monitoring-test-uss_qualifier-geoawareness_cis-test-reports
|
1.39 KB |
sha256:da5c309589c54d75618bd678d8cb8e6753e37700b64d8b5c892c1ee8fbe8af97
|
|
|
monitoring-test-uss_qualifier-geospatial_comprehension-test-logs
|
18 KB |
sha256:2ff7dd0fe57516816afa910d3c5867cf0e139b07e4f14d5abc5c00c808dc01bc
|
|
|
monitoring-test-uss_qualifier-geospatial_comprehension-test-reports
|
23.2 KB |
sha256:95f8e98448b5f8b0c9da17891ffd9704abc8dabc13d0ac9cf5d0a072e290986a
|
|
|
monitoring-test-uss_qualifier-message_signing-test-logs
|
645 KB |
sha256:0de773e0a258f3b73883ade8c8dd47d6d76c01c022071f8e78217e4d03076e2f
|
|
|
monitoring-test-uss_qualifier-message_signing-test-reports
|
1.2 MB |
sha256:9c484405596346ec3059a48e2384b7582687d27f7ab6a501c77ed259c62d2df0
|
|
|
monitoring-test-uss_qualifier-minimal_probing-test-logs
|
103 KB |
sha256:edcaaf3cb59eba286278dcf7cd85a50a423bba5a0342bd3a3c3f79f4c170850a
|
|
|
monitoring-test-uss_qualifier-minimal_probing-test-reports
|
305 KB |
sha256:36b3981e4258ea70fa731364f488a2804409c6265ef909645e1d742d7e919e57
|
|
|
monitoring-test-uss_qualifier-netrid_v19-test-logs
|
573 KB |
sha256:f3f0d450c15796544f6f1de72f7c54d71d4bb10e17f1a0cf42f4f68645124670
|
|
|
monitoring-test-uss_qualifier-netrid_v19-test-reports
|
1.83 MB |
sha256:0b7269ad69deae94e2c1c8cc0833e89cf50347f532ccfaff8fd997a7ff16646c
|
|
|
monitoring-test-uss_qualifier-netrid_v22a-test-logs
|
600 KB |
sha256:6de920f92c0ac295d6c4af44658340bd761be8b316593e069424408ba8817fcc
|
|
|
monitoring-test-uss_qualifier-netrid_v22a-test-reports
|
1.95 MB |
sha256:4ac54813182ec60e3f59a0e20254caa0bdb44f3e7c7acf9ad0c9f7727c0b0aff
|
|
|
monitoring-test-uss_qualifier-noop-test-logs
|
17.8 KB |
sha256:4f932cd0c58f3730fa60c6e24abe174d9ce1ea53121d383d1d8ccebc1db93f16
|
|
|
monitoring-test-uss_qualifier-noop-test-reports
|
10.3 KB |
sha256:767ce666a680cfd6effc668d5e0bd10cb3a270bce2ba4896aad8f8964e19e344
|
|
|
monitoring-test-uss_qualifier-uspace-test-logs
|
626 KB |
sha256:059ac946f93f102e80064fe31b4509b5b1f32d9b0bee024275b08d4e2050b172
|
|
|
monitoring-test-uss_qualifier-uspace-test-reports
|
2.44 MB |
sha256:d9678ae51afc59a0755a86644040881acaf59abb577a59df57887767c36d8d84
|
|
|
monitoring-test-uss_qualifier-utm_implementation_us-test-logs
|
579 KB |
sha256:9b679d5a310c7964ebc5bd9b94b2709d7814786a6f91ac14325e3d2b8754c6ce
|
|
|
monitoring-test-uss_qualifier-utm_implementation_us-test-reports
|
1.34 MB |
sha256:38d6a0d93c9c1b1a23ea42ba28a989422d8dea761bce51e44deb08428a89e56b
|
|