-
Notifications
You must be signed in to change notification settings - Fork 314
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
encoding on windows with expect_known_output #694
Comments
What's your |
2.0.0. Current dev version does not work for me either. |
Looks like this is a bug indeed. The strings are actually equal, but they have different marked encodings, one is "unknown", the other one "latin1". I don't have an immediate workaround unfortunately, except for using |
This might be related to a bug in R that is fixed in R-devel: wch/r-source@64f889d . ( |
@patperry they don't seem related to me. |
you know better than I do. any time I see a curly quote and "Windows encoding" I assume it's this CP1252/Latin-1 issue |
I do not get the bug output with testthat 2.0.1 and R 3.5.1 on Windows. |
Closing since it seems like this has fixed itself in the mean time. |
I'm having difficulties with
expect_known_output
on windows due to encoding issues. The reference file was created on unix, and tests pass there. On windows several tests fail. I checked the ouput of my functions, it is UTF-8, so there is no reason why a mismatch between output and reference file should occur.There seems to be a problem in
testthat
, as the following reprex suggests:The text was updated successfully, but these errors were encountered: