game-ci / unity-test-runner

Run tests for any Unity project
https://github.com/marketplace/actions/unity-test-runner
MIT License
210 stars 135 forks source link

Error: Only 65535 characters are allowed #214

Closed MrGadget1024 closed 4 months ago

MrGadget1024 commented 1 year ago

Still getting this error, not fixed by https://github.com/game-ci/unity-test-runner/commit/b9980d6db77b429efa66b950aef387eea018775d

- name: Run editor Tests
  continue-on-error: true
  uses: game-ci/unity-test-runner@main
Processing file editmode-results.xml...
Trying to open artifacts/editmode-results.xml
File artifacts/editmode-results.xml parsed...
Start analyzing results: editmode-results.xml
⚠️ editmode-results.xml - 991/1003, skipped: 12 - Passed in 107.210s
=================
Analyze result:
⚠️ Test Results - 991/1003, skipped: 12 - Passed in 107.210s
Posting results for 953944bREDACTEDf5fc69cf8e7c906d266cef5ef
Error: Invalid request.

Only 65535 characters are allowed; 75929 were supplied.
MrGadget1024 commented 1 year ago

Any progress on this, or ideas?

timcassell commented 1 year ago

I'm surprised #206 didn't fix it. You can work around it by using another test reporting tool (see comments in #142).

MrGadget1024 commented 1 year ago

I'm surprised #206 didn't fix it. You can work around it by using another test reporting tool (see comments in #142).

Are we talking about the same point of failure? The failure I'm getting is before the archive step...

image

The error is in the Run editor Tests step...

image

Archive and Publish are working fine

image

Files inside the zip archive

image

I don't know where the "75929 were supplied" comes from but it's clearly not these files.

timcassell commented 1 year ago

Yes, that looks like the same error to me. I see you are using another test reporter. Remove githubToken: ${{ secrets.GITHUB_TOKEN }} to disable the built-in test reporter.

MrGadget1024 commented 1 year ago

Yes, that looks like the same error to me. I see you are using another test reporter. Remove githubToken: ${{ secrets.GITHUB_TOKEN }} to disable the built-in test reporter.

This got rid of the error but leaving this ticket open as the issue still exists. Will work on a nicer test reporter tomorrow.

johanhelsing-attensi commented 7 months ago

Also hitting this one. Let me know if there's anything I can do to help.

webbertakken commented 7 months ago

I think some worked around this by parallelising tests to different jobs. This might not be a solution for everyone though.


One idea we've had is to group logs on a per test suite basis.

We could most likely achieve that by optionally writing the unity logs to a file instead of stdout, and then doing some regex to specify the delimiters.

MrGadget1024 commented 4 months ago

@davidmfinol Should this be closed now?

davidmfinol commented 4 months ago

@MrGadget1024 can you confirm it works OK now if you use game-ci/unity-test-runner@main?

MrGadget1024 commented 4 months ago

@davidmfinol Someone else like @johanhelsing-attensi will have to check...My workflow has changed and I wouldn't be able to reproduce it now.

migwellian commented 4 months ago

Hello, I can confirm it is fixed - I had the same issue so I switched from game-ci/unity-test-runner@v4 to game-ci/unity-test-runner@main and it fixed the issue.

davidmfinol commented 4 months ago

Fix released in v4.3.1