You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am generating junit xml using golang and github.com/jstemmer/go-junit-report/v2@latest. Sometimes, on failure, it produces XML with an empty failure element. This produces a parse error:
Run dorny/test-reporter@v1
Action was triggered by pull_request: using SHA from head of source branch
...
Using test report parser 'java-junit'
Creating test report XXXX
Processing test results for check run XXXX
Creating check run XXXX
Creating report summary
Generating check run summary
Error: TypeError: Cannot read properties of undefined (reading 'split')
Adding a value, eg <failure message="Failed">bla</failure resolves this issue. I do not know if empty element is valid in junit format. If it is not valid, then I should open an issue with github.com/jstemmer/go-junit-report.
I am experiencing this same issue, except with XML output from rspec_junit_formatter.
Run dorny/test-reporter@v1
Check runs will be created with SHA=XXX
> Listing all files tracked by git
Found 4538 files tracked by GitHub
Using test report parser 'java-junit'
> Creating test report Rspec Test Results
Processing test results for check run Rspec Test Results
Creating check run My Awesone Test
Creating report summary
Generating check run summary
Creating annotations
Error: TypeError: Cannot read properties of undefined (reading 'split')
My failure does occur further along in, however, in the Creating annotations step. Since we've used the same reporter, it may be something to do with the parser which results in:
I am generating junit xml using golang and github.com/jstemmer/go-junit-report/v2@latest. Sometimes, on failure, it produces XML with an empty failure element. This produces a parse error:
Sample XML:
Adding a value, eg
<failure message="Failed">bla</failure
resolves this issue. I do not know if empty element is valid in junit format. If it is not valid, then I should open an issue with github.com/jstemmer/go-junit-report.My action:
The text was updated successfully, but these errors were encountered: