Skip to content
Security Test Workflow

Delete detector successfully if workflow is missing (#790) #1285

Sign in to view logs

Delete detector successfully if workflow is missing (#790)

Delete detector successfully if workflow is missing (#790) #1285

Triggered via pull request January 17, 2024 21:59
@engechasengechas
synchronize #809
engechas:backport-790-to-2.x
Status Failure
Total duration 3m 29s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

security-test-workflow.yml

on: pull_request
Matrix: Build and test SecurityAnalytics
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
Build and test SecurityAnalytics (11)
Process completed with exit code 7.
Build and test SecurityAnalytics (21)
Process completed with exit code 7.
Build and test SecurityAnalytics (17)
Process completed with exit code 7.
Build and test SecurityAnalytics (11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build and test SecurityAnalytics (21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build and test SecurityAnalytics (17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v1, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/