-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Windows] Cannot be encoded into charset windows-1252 build error in LogManager #299
Comments
Other CI failures (with the same issue): https://github.com/graalvm/mandrel/actions/runs/12119015627/job/33786195712 |
https://github.com/graalvm/mandrel/actions/runs/12190610416/job/34008912174#step:10:8910 (JDK 24 windows failure) |
This seems to be gone with latest CI runs. We'll see if it re-surfaces. Past passing runs: |
quarkusFullMicroProfile
test with JDK 21/24 CI fails on Windows with:It might be that we ought to set the encoding explicitly and not assume the default encoding which - I think - is
windows-1252
on windows systems by default.CI failure:
https://github.com/graalvm/mandrel/actions/runs/12092054635/job/33721720218#step:10:8946
The text was updated successfully, but these errors were encountered: