Skip to content

chore(accident-notification): organize utils #69681

chore(accident-notification): organize utils

chore(accident-notification): organize utils #69681

Triggered via pull request December 11, 2024 14:49
Status Failure
Total duration 54m 10s
Artifacts 1

pullrequest.yml

on: pull_request
Matrix: build
Matrix: e2e
Matrix: linting
Matrix: tests
success
7s
success
Fit to window
Zoom out
Zoom in

Annotations

39 errors and 2 warnings
build (application-system-form)
Process completed with exit code 1.
build (application-system-api)
Property 'isReportingOnBehalfOfEmployee' does not exist on type 'typeof import("/__w/island.is/island.is/libs/application/templates/accident-notification/src/utils/miscUtils")'.
build (application-system-api)
Cannot find module './isFatalAccident' or its corresponding type declarations.
build (application-system-api)
Process completed with exit code 1.
build (api)
Property 'isReportingOnBehalfOfEmployee' does not exist on type 'typeof import("/__w/island.is/island.is/libs/application/templates/accident-notification/src/utils/miscUtils")'.
build (api)
Cannot find module './isFatalAccident' or its corresponding type declarations.
build (api)
Process completed with exit code 1.
tests (services-auth-delegation-api)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
tests (services-auth-delegation-api)
The operation was canceled.
tests (portals-my-pages-assets,portals-my-pages-consent,portals-my-pages-constants,portals-my-pag...
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
linting (auth-admin-web,auth-api-lib,auth-nest-tools,auth-scopes,auth-shared)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
linting (clients-auth-ids-api,clients-auth-public-api,clients-car-recycling,clients-charge-fjs-v2...
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
linting (logging)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
linting (logging)
The operation was canceled.
linting (clients-syslumenn,clients-transport-authority-digital-tachograph-drivers-card,clients-tr...
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
linting (api-domains-communications,api-domains-company-registry,api-domains-content-search,api-d...
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
linting (localization)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
linting (localization)
The operation was canceled.
tests (nest-pagination,nest-problem,nest-sequelize,nest-swagger)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
linting (judicial-system-api,judicial-system-audit-trail,judicial-system-auth,judicial-system-con...
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
linting (shared-problem,shared-translations,shared-types,shared-utils)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
linting (shared-problem,shared-translations,shared-types,shared-utils)
The operation was canceled.
linting (services-user-profile,services-xroad-collector)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
tests (application-template-api-modules,application-template-loader,application-templates-acciden...
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
linting (clients-transport-authority-vehicle-plate-renewal,clients-transport-authority-vehicle-pr...
The self-hosted runner: i-0def6fc5b9ae4c94b lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
linting (clients-user-profile,clients-vehicle-service-fjs-v1,clients-vehicles,clients-vehicles-mi...
The self-hosted runner: i-041ed7f6c61c924b6 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
linting (clients-rsk-relationships,clients-sessions,clients-signature-collection,clients-smart-so...
The self-hosted runner: i-083aa92cda4dc3ab3 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
linting (testing-containers,testing-e2e,testing-fixtures,testing-nest)
The self-hosted runner: i-088688175f8f6f831 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
tests (native-app)
The self-hosted runner: i-00e5e901ecb03bd2d lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
linting (clients-driving-license,clients-driving-license-book,clients-ehic-client-v1,clients-elec...
The self-hosted runner: i-0ebd7be5ebbe53e39 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
tests (portals-my-pages-law-and-order,portals-my-pages-licenses,portals-my-pages-occupational-lic...
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
tests (portals-my-pages-law-and-order,portals-my-pages-licenses,portals-my-pages-occupational-lic...
The self-hosted runner: i-029308911428b1ba0 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
success
Process completed with exit code 1.
run-shellcheck
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
run-shellcheck
Unexpected input(s) 'fail-level', valid inputs are ['github_token', 'level', 'reporter', 'filter_mode', 'fail_level', 'fail_on_error', 'reviewdog_flags', 'path', 'pattern', 'check_all_files_with_shebangs', 'exclude', 'shellcheck_flags']

Artifacts

Produced during runtime
Name Size
pr-event
226 Bytes