-
Notifications
You must be signed in to change notification settings - Fork 43
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
Tests are failing with the forked vt100
crate
#50
Comments
I didn't change code related to those failing tests. The vt100 seems to be unmaintained, so at some point these tests might need to be fixed in this repo. But for now I think it's safe to ignore them. |
Okay good to hear. I was only concerned because I had packaged mprocs here, and I was having test failures (and therefore build failures). If you think it's okay I'll just go ahead and disable the tests. Just out of curiosity, do you think it's likely that those faulty tests will be fixed/removed in the future, either by this fork of vt100 or upstream? |
After quickly checking a couple of failing tests, it is not clear which behavior is correct - expected or actual. |
Alright. I'll disable the tests for |
Hello, Here is the log I get: https://gist.github.com/GaetanLepage/431d34fe2eafe8480e0eca91101e96a2 Am I doing something wrong ? Thank you very much for your help ! PS: Why does the |
currently it looks like only one test fails:
|
I ran |
Yes, tests were fixed. Thank you. |
First of all, due to the crate rename, all references to
vt100
need to be replaced withmprocs_vt100
.But even after I fixed that by adding
use mprocs_vt100 as vt100;
where necessary, quite a few tests are still failing. See log.test-fail.log
The text was updated successfully, but these errors were encountered: