Roadmap: https://github.com/cobbler/cobbler/wiki/Roadmap Meeting Room: https://meet.opensuse.org/cobbler
A workflow run is triggered regardless of the result of the previous workflow.
The docs for test reporter mention that public forks are not entitled to create check jobs
And the whole reason for a separate workflow is to put it in master branch
Note: This event will only trigger a workflow run if the workflow file is on the default branch.
I was expecting a failure
If that's okay with you
Nvm saw the example from the Action.
So yeah. Cleanup what you want and then I'll merge. If it fails we fix it with a followup PR. Not nice but we have no other choice afaik.
So we can do this right ahead
it kinda is
but failed
Ah okay
Yeah but that is a problem with XML?
Found it: The outer<testsuites> is not expected and causes issues. trimming those and it works.
Hmm
I guess that's the problem
Someone being naughty and not follows the spec
I'm not sure who though xD
k, should be fine now
Goddamit
It seems that Github Actions sucks dick
The test report cannot be bigger than 65k bytes and no screenshots, no links, nothing
As a bonus Check Jobs cannot be properly positioned in multi-workflow build
So the result will pop under random workflows
I suggest Allure and GitHub pages
We can paste the unit test results there too
Maximum report size is 65535 bytes. Input parameters list-suites and list-tests will be automatically adjusted if max size is exceeded.
Check Runs are created for specific commit SHA. It's not possible to specify under which workflow test report should belong if more workflows are running for the same SHA. Thanks to this GitHub "feature" it's possible your test report will appear in an unexpected place in GitHub UI. For more information, see #67.
That's why we haven't seen the report: it was hidden under the different workflow tab
Okay well the 65kb is a blocker. The other thing is just inconvenient. Can we maybe upload the test results to codacy?
Afaik they support test results