Skip to content
Scheduled Continuous Integration

Scheduled Continuous Integration #1380

Sign in to view logs

Scheduled Continuous Integration

Scheduled Continuous Integration #1380

Triggered via schedule September 30, 2023 09:03
@fallwithfallwith
⁠ 806b0a9
dev
Status Failure
Total duration 28m 19s
Artifacts –

ci_cron.yml

on: schedule
Matrix: infinite_tracing
Matrix: multiverse
Matrix: unit_tests
run_rubocop
35s
run_rubocop
Notify slack fail
5m 31s
Notify slack fail
Notify slack success
5s
Notify slack success
Fit to window
Zoom out
Zoom in

Annotations

1 error and 11 warnings
unit_tests (2.7.8)
Final attempt failed. Child_process exited with error code 1
multiverse (database, 3.0.6)
Attempt 1 failed. Reason: Child_process exited with error code 1
multiverse (frameworks, 3.1.4)
Attempt 1 failed. Reason: Child_process exited with error code 1
multiverse (rails, 3.0.6)
Attempt 1 failed. Reason: Child_process exited with error code 1
multiverse (rails, 3.1.4)
Attempt 1 failed. Reason: Child_process exited with error code 1
multiverse (frameworks, 3.0.6)
Attempt 1 failed. Reason: Child_process exited with error code 1
multiverse (frameworks, 2.7.8)
Attempt 1 failed. Reason: Child_process exited with error code 1
multiverse (background_2, 2.7.8)
Attempt 1 failed. Reason: Child_process exited with error code 1
multiverse (rails, 2.7.8)
Attempt 1 failed. Reason: Child_process exited with error code 1
multiverse (background_2, 3.0.6)
Attempt 1 failed. Reason: Child_process exited with error code 1
unit_tests (2.7.8)
Attempt 1 failed. Reason: Child_process exited with error code 1
Notify slack fail
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/