Closed tandeday closed 3 years ago
Hi @tandeday
Thanks for trying to use this action and raising this issue. I am currently on vacation but from the error I can guess that it is failing due to limits on the output
field of the checks api.
Not sure what can b done about that but I'll have a look next week.
In the meantime, would you mind sharing the trx if not confidential?
Related: github/docs#2403 zyborg/dotnet-tests-report#6
This is not urgent so no rush. I cannot share the TRX file publicly, but perhaps with you personally. Let's have a look together when you are back from vacation.
@tandeday Based on the linked issues in the comment above it is clear this is a hard limit on the GitHub checks API and there is no solution to that limit.
So here's what I propose:
skip_test_report
and create an empty check with a simple overall pass or fail status. ORThoughts?
Once we have some consensus on one of options above or a better option you could suggest then we can talk about implementation. Please feel free to contribute if you have time otherwise I'll try to address this when I can find free time.
Things have changed as we have had a firing round, and this is no longer in scope. I will suggest that the default behavior is the safest without generating a test report (or at least just create a summary that will fit in the block), and that the full report is only shown if explicitly enabled, and that the documentation clearly shows that there is a hard limit for the size.
Thanks
Created a new release https://github.com/NasAmin/trx-parser/releases/tag/v0.1.0
From v0.1.0
onwards, trx-parser
will only report failed tests
TODO: Update the readme to reflect the new behaviour
I am kicking the tires on this action using a project with about 1000 tests. Unfortunately it fails. Any suggestions?