Skip to content

Conversation

@AJIOB
Copy link
Contributor

@AJIOB AJIOB commented Jan 8, 2026

The problem usually occurs when VS_UNICODE_OUTPUT is set. This is a @AudranDoublet #1835 and @exoosh #2483 fixes with working tests: thank you!

Should fix issues #1830 and #909

@AJIOB AJIOB force-pushed the VS_UNICODE_OUTPUT_fix_2 branch from 0e300e6 to edde193 Compare January 8, 2026 07:53
@codecov-commenter
Copy link

codecov-commenter commented Jan 8, 2026

Codecov Report

❌ Patch coverage is 76.92308% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 71.17%. Comparing base (951e247) to head (4f1f083).
⚠️ Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
src/compiler/msvc.rs 72.72% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2544      +/-   ##
==========================================
- Coverage   71.17%   71.17%   -0.01%     
==========================================
  Files          64       64              
  Lines       35592    35588       -4     
==========================================
- Hits        25334    25328       -6     
- Misses      10258    10260       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@codspeed-hq
Copy link

codspeed-hq bot commented Jan 10, 2026

CodSpeed Performance Report

Merging this PR will not alter performance

Comparing AJIOB:VS_UNICODE_OUTPUT_fix_2 (4f1f083) with main (f66b044)

Summary

✅ 27 untouched benchmarks
⏩ 2 skipped benchmarks1

Footnotes

  1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@sylvestre
Copy link
Collaborator

could you please add a test to make sure we don't regress? thanks

The problem usually occurs when VS_UNICODE_OUTPUT is set.
This is a @AudranDoublet mozilla#1835 and @exoosh mozilla#2483 fixes with working tests: thank you!

Should fix issues mozilla#1830 and mozilla#909
@AJIOB AJIOB force-pushed the VS_UNICODE_OUTPUT_fix_2 branch 2 times, most recently from e63289b to 7b70bc7 Compare January 12, 2026 08:03
@AJIOB AJIOB force-pushed the VS_UNICODE_OUTPUT_fix_2 branch from 7b70bc7 to 4f1f083 Compare January 12, 2026 08:12
@AJIOB
Copy link
Contributor Author

AJIOB commented Jan 12, 2026

could you please add a test to make sure we don't regress? thanks

@sylvestre , done

@sylvestre
Copy link
Collaborator

could you please add a test to make sure we don't regress? thanks

@sylvestre , done

to make sure i understand, what you added in the CI was previously failing to build, right ?
thanks

@AJIOB
Copy link
Contributor Author

AJIOB commented Jan 12, 2026

Yes, it previously fails.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants