-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Load module on remote workers from master #21647
Conversation
@vtjnash is the right person to review this. |
Testing is quite tricky as it requires workers on remote hosts. I have something that might work (see below), but I don't know much about the test environment.
|
Is it possible this could be backported to v0.5 (v0.5.2)? |
Rerun tests |
Closes #21179
Packages such as `Requires.jl` need to be notified when a package is successfully loaded. Currently we have to resolve to a horrible hack that overrides `Base.require`. In a post 265 world this is no longer feasible.
…se. (#21651) * Fix bug in nprocs()/nworkers()/procs() in non :all_to_all topology case.
This reverts commit 6941f04.
This reverts commit 89572e6.
This reverts commit 1509a6f.
…ters" This reverts commit 5fc0989.
This reverts commit d8497f7.
This reverts commit 0e33492.
This reverts commit 2d30573.
This reverts commit 3034c0f.
This reverts commit a49ebe2.
This reverts commit aa79523.
This reverts commit ad67ab5.
This reverts commit 092a3c9.
This reverts commit daf9e2f.
This reverts commit b1fe1b9.
This reverts commit bb0e335.
This reverts commit cb9f8cd.
This reverts commit 133af84.
This reverts commit 9061644.
This reverts commit 70753f4.
This reverts commit 0f5ba42.
This reverts commit dd8e6dd.
Test for Issue #19960
end | ||
|
||
catch | ||
@test false |
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.
why is the catch here at all?
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.
Given your comment, it probably doesn't need to be there.
(As you've probably guessed I don't really understand testing)
I thought that there had to be an explicit @test
failure, rather than just a thrown error from the try block.
I can remove it.
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.
something went wrong with the rebase as well, when you do git rebase -i origin/master
you should remove all the commits that aren't yours from the list that shows up, and when you're happy with the local state of the branch (just your commits, on top of latest master) you can push to the glp/remote_loading
branch of your fork with --force
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.
Yes I can see that it's screwed up.
But also test/compile.jl
is showing extra changes (changes made to master after my original PR but before the update). I don't think those changes should be showing here.
I don't know how to get out of this mess, except closing this and making a new PR.
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.
You can amend a pull request in place with an interactive rebase, usually git rebase -i origin/master
assuming origin is JuliaLang/julia and you've done a git fetch origin
recently. Once the local copy is cleaned up, do git push --force GregPlowman branchname
assuming GregPlowman is a remote for your fork
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 Tony!
I've already created a replacement PR, but I'll certainly try to follow your advice next time.
Replaced by #21695 |
Fix #19960