Skip to content
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

Test Fails on Windows 10. #26

Open
lijinpei opened this issue Dec 1, 2019 · 1 comment
Open

Test Fails on Windows 10. #26

lijinpei opened this issue Dec 1, 2019 · 1 comment
Assignees

Comments

@lijinpei
Copy link
Contributor

lijinpei commented Dec 1, 2019

Platform: win10 1903, chez scheme installed from chocoloty
How to reproduce:
1. clone nanopass from github
2. scheme test-all.ss
What you expect to see:
all test passes.
What you got:

Running error-messages test suite...
  Testing run-time-error-messages ...
!!! expected error message "Exception in with-output-language: expected list of symbol but recieved x in field x* of (lambda (x* ...) body* ... body) from expression (quote x) at character position 31709 of tests/unit-tests.ss" does not match "Exception in with-output-language: expected list of symbol but recieved x in field x* of (lambda (x* ...) body* ... body) from expression (quote x) at character position 32575 of tests/unit-tests.ss"
#f
Ran 1 tests with 0 successes, 1 failures, and 0 exceptions

The failed test is this one

(test-suite error-messages
In fact, it is correct up to the character offset.

@akeep
Copy link
Member

akeep commented Dec 1, 2019

Thanks for the bug report, the precision on the character offsets has been a bit of a problem for this test suite for a while, and one I've meant to address.

I do most of my development on macOS, where the file is a unix-style text file with single-character line-endings. The Windows (or DOS) style file endings which are two-character cause the count to be slightly different.

I need to come up with a way to make this a bit more permissive, but I've not done it yet. Thanks for the bug report!

@akeep akeep self-assigned this Dec 1, 2019
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

No branches or pull requests

2 participants