-
Notifications
You must be signed in to change notification settings - Fork 11
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
Testing can leave a stale Manifest.toml, leading to test failures #70
Comments
Thanks for trying to reproduce! It turns out this was a stale manifest in my development environment. Perhaps the |
Ok, I've done some fixes in #71 which should make the tests a lot cleaner. Including trying to run the server subprocesses in the correct test environment. Hopefully that'll fix the root cause here. |
I think the |
After #55, I get the following somewhat inscrutable test failure on my machine, on Julia 1.10.
@filchristou - I think it's best to resolve this before releasing a new RemoteREPL version. But once it's sorted, I think we can just release RemoteREPL-1.0 and get into the major version numbers. It's an incompatible release in some sense, since we've bumped the
PROTOCOL_VERSION
.To reproduce, make sure you've got an ssh server running on your machine and can log into localhost so the tunnel will work.
The text was updated successfully, but these errors were encountered: