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

FIx misleading addprocs documentation #10459

Merged
merged 1 commit into from
Mar 10, 2015
Merged

Conversation

mweastwood
Copy link
Contributor

I'm not 100% sure of this change, but my experimentation seems to indicate that this more accurately reflects addprocs's behavior.

I'm not 100% sure of this change, but my experimentation seems to indicate that this more accurately reflects `addprocs`'s behavior.
@mbauman mbauman added domain:docs This change adds or pertains to documentation domain:parallelism Parallel or distributed computation labels Mar 9, 2015
@amitmurthy
Copy link
Contributor

Thanks @mweastwood .
Merging this as it is only a doc change.
The Travis error, while unrelated, probably needs looking into.

amitmurthy added a commit that referenced this pull request Mar 10, 2015
FIx misleading `addprocs` documentation
@amitmurthy amitmurthy merged commit e917b99 into JuliaLang:master Mar 10, 2015
@tkelman
Copy link
Contributor

tkelman commented Mar 10, 2015

Travis failure was caused by ca79bec and fixed by c864e79 - tsk tsk, pushing without running the tests locally

@amitmurthy
Copy link
Contributor

Just curious - how did the 64-bit linux and osx tests pass with this typo?

@tkelman
Copy link
Contributor

tkelman commented Mar 10, 2015

Because travis does a fetch of the PR merge commit when the build starts, those builds started after the fix was pushed to master, the failed build started before

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain:docs This change adds or pertains to documentation domain:parallelism Parallel or distributed computation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants