Skip to content

fix(plc4j/profinet): Sonar fix regex matching zeo chars #358

fix(plc4j/profinet): Sonar fix regex matching zeo chars

fix(plc4j/profinet): Sonar fix regex matching zeo chars #358

Triggered via push May 11, 2023 17:30
Status Failure
Total duration 6h 0m 40s
Artifacts
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 10 warnings
test (18, macos-latest)
Process completed with exit code 1.
test (17, macos-latest)
Process completed with exit code 1.
test (18, ubuntu-latest)
The job running on runner GitHub Actions 117 has exceeded the maximum execution time of 360 minutes.
test (18, ubuntu-latest)
The operation was canceled.
test (17, ubuntu-latest)
The job running on runner GitHub Actions 35 has exceeded the maximum execution time of 360 minutes.
test (17, ubuntu-latest)
The operation was canceled.
test (11, macos-latest)
The job running on runner GitHub Actions 4 has exceeded the maximum execution time of 360 minutes.
test (11, macos-latest)
The operation was canceled.
test (11, ubuntu-latest)
The job running on runner GitHub Actions 121 has exceeded the maximum execution time of 360 minutes.
test (11, ubuntu-latest)
The operation was canceled.
test (17, windows-latest)
1 issue was detected with this workflow: Please make sure that every branch in on.pull_request is also in on.push so that Code Scanning can compare pull requests against the state of the base branch.
test (11, windows-latest)
1 issue was detected with this workflow: Please make sure that every branch in on.pull_request is also in on.push so that Code Scanning can compare pull requests against the state of the base branch.
test (18, windows-latest)
1 issue was detected with this workflow: Please make sure that every branch in on.pull_request is also in on.push so that Code Scanning can compare pull requests against the state of the base branch.
test (18, windows-latest)
Failed to restore: The operation cannot be completed in timeout.
test (18, macos-latest)
1 issue was detected with this workflow: Please make sure that every branch in on.pull_request is also in on.push so that Code Scanning can compare pull requests against the state of the base branch.
test (17, macos-latest)
1 issue was detected with this workflow: Please make sure that every branch in on.pull_request is also in on.push so that Code Scanning can compare pull requests against the state of the base branch.
test (18, ubuntu-latest)
1 issue was detected with this workflow: Please make sure that every branch in on.pull_request is also in on.push so that Code Scanning can compare pull requests against the state of the base branch.
test (17, ubuntu-latest)
1 issue was detected with this workflow: Please make sure that every branch in on.pull_request is also in on.push so that Code Scanning can compare pull requests against the state of the base branch.
test (11, macos-latest)
1 issue was detected with this workflow: Please make sure that every branch in on.pull_request is also in on.push so that Code Scanning can compare pull requests against the state of the base branch.
test (11, ubuntu-latest)
1 issue was detected with this workflow: Please make sure that every branch in on.pull_request is also in on.push so that Code Scanning can compare pull requests against the state of the base branch.