Skip to content
Scheduled Continuous Integration

Scheduled Continuous Integration #1326

Sign in to view logs

Scheduled Continuous Integration

Scheduled Continuous Integration #1326

Triggered via schedule September 4, 2023 09:03
@fallwithfallwith
⁠ 6747d35
dev
Status Success
Total duration 26m 12s
Artifacts –

ci_cron.yml

on: schedule
Matrix: infinite_tracing
Matrix: multiverse
Matrix: unit_tests
run_rubocop
30s
run_rubocop
Notify slack fail
6s
Notify slack fail
Notify slack success
4m 16s
Notify slack success
Fit to window
Zoom out
Zoom in

Annotations

13 warnings
multiverse (frameworks, 3.1.4)
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, 2.7.8)
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 (rails, 3.0.6)
Attempt 1 failed. Reason: Child_process exited with error code 1
unit_tests (3.2.2)
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 (background_2, 3.0.6)
Attempt 1 failed. Reason: Child_process exited with error code 1
infinite_tracing (2.5.9)
Attempt 1 failed. Reason: Child_process exited with error code 1
unit_tests (2.5.9)
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
unit_tests (3.3.0-preview1)
Attempt 1 failed. Reason: Child_process exited with error code 1
Notify slack success
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/