Skip to content
PR-check

report generation should properly handle unparsable test results - it should still process other test results and not just fail completely upon the first invalid result #461

Sign in to view logs

report generation should properly handle unparsable test results - it should still process other test results and not just fail completely upon the first invalid result

report generation should properly handle unparsable test results - it should still process other test results and not just fail completely upon the first invalid result #461

Triggered via pull request February 7, 2024 12:17
@qkrorlqrqkrorlqr
opened #357
Status Success
Total duration 58m 11s
Artifacts –

pr.yaml

on: pull_request_target
check-running-allowed
5s
check-running-allowed
Build and test  /  Start self-hosted runner
1m 46s
Build and test / Start self-hosted runner
Build and test  /  Prepare runner [id=dp7uba78nbf0g93dii0g]
1m 10s
Build and test / Prepare runner [id=dp7uba78nbf0g93dii0g]
Build and test  /  ...  /  Build and test relwithdebinfo [id=dp7uba78nbf0g93dii0g ip=195.242.16.77]
53m 11s
Build and test / Build and test NBS [id=dp7uba78nbf0g93dii0g ip=195.242.16.77] / Build and test relwithdebinfo [id=dp7uba78nbf0g93dii0g ip=195.242.16.77]
Build and test  /  Release self-hosted runner dp7uba78nbf0g93dii0g
1m 10s
Build and test / Release self-hosted runner dp7uba78nbf0g93dii0g
Fit to window
Zoom out
Zoom in

Annotations

1 warning
check-running-allowed
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/github-script@v6. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.