-
Notifications
You must be signed in to change notification settings - Fork 110
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
dont assume we can find source code for loaded packages #460
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Is there any feasible way to test this? I worry about regressions...
For testing, you can force it with something like (assuming you have multiple precompile files stored for Example):
but I am not sure how to cause it to happen in normal usage |
I guess we should just go ahead with this, since that test is pretty artificial and would presumably fail at a slightly later line. |
Could we make a release with this commit? I am also dealing with the PackageCompiler issue 🙂 |
I was hoping to add something else, but let's get this out as-is. |
Ah i see. I just wanted to make sure it wasn't going to get forgotten! |
Ugh, I should have read this more carefully. How on earth did the tests pass, I am really confused... |
https://travis-ci.org/github/timholy/Revise.jl/builds/677646144 claims it's the right commit, 15a561a, and shows all tests passing. Yet when I try it locally I get
as well as an error upon startup. Explaining it as a weird Travis error also doesn't entirely make sense, because AppVeyor did the same thing: https://ci.appveyor.com/project/timholy/revise-jl/builds/32330643. Can anyone make sense of this? |
This is designed to catch issues like what happened in #460, but also more generally improve test coverage.
This is designed to catch issues like what happened in #460, but also more generally improve test coverage.
This is designed to catch issues like what happened in #460, but also more generally improve test coverage.
This can happen when Revise is put into a sysimage and it's dependencies are no longer in the Project/Manifest (as happens in JuliaLang/PackageCompiler.jl#391)