Skip to content
Security Test Workflow

support object fields in aggregation based sigma rules #1273

Sign in to view logs

support object fields in aggregation based sigma rules

support object fields in aggregation based sigma rules #1273

Triggered via pull request January 13, 2024 09:09
@sbcd90sbcd90
synchronize #789
sbcd90:aggr_fixes_object
Status Failure
Total duration 3m 51s
Artifacts –

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 (17)
Process completed with exit code 7.
Build and test SecurityAnalytics (21)
Process completed with exit code 7.
Build and test SecurityAnalytics (11)
The operation was canceled.
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/
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 (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/