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
There is nothing (extra) in the logs other than the "report written to ..." message. However, it is a bit malformed, looks like some color/control sequences for the terminal don't work properly:
...
25lJUNIT report written to /home/runner/work/fancy-boards/fancy-boards/build/report.junit.xml
25h
Update: It seems like there is indeed a weird failing test, that fails on CI but not locally. It seems like Vitest incorrectly reads the inline snapshot on CI, I'll try to come up with a reproduction.
The text was updated successfully, but these errors were encountered:
rChaoz
changed the title
Exit code 1 in CI without any errors when reporting is enabled
Exit code 1 in Github Actions without any errors when reporting is enabled
Jan 30, 2025
Welp, turns out it was a weird line endings issue - CRLF vs LF + .gitattributes + I use Windows locally and actions used Linux. The root cause was a file imported with import string from "./path?raw"
Describe the bug
I'm not sure how to debug this very well. My CI started failing since I added the following config to my
vite.config.ts
:There is nothing (extra) in the logs other than the "report written to ..." message. However, it is a bit malformed, looks like some color/control sequences for the terminal don't work properly:
Update: It seems like there is indeed a weird failing test, that fails on CI but not locally. It seems like Vitest incorrectly reads the inline snapshot on CI, I'll try to come up with a reproduction.
The text was updated successfully, but these errors were encountered: