-
-
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
More robust detection of user code #9581
Conversation
It should be clarified that the problems this fixes arose in files that defined their own modules living inside |
OSX has timed out on this twice now. Anybody have insights? I'm guessing that since Linux & Windows are both working, it's probably OK. |
@timholy the Homebrew dependencies are downloaded from SourceForge which is frequently unreliable. @staticfloat should we maybe copy over all of the dependencies that we need on Travis to the tap, so we can keep them on more-reliable S3? Upstream Homebrew is in need of a source of funds before they'll consider switching to S3 themselves. |
I see you must have restarted again, thanks. I'll merge. |
More robust detection of user code
Am I right in thinking that now the recommended approach is just to add the backport_pending label? |
@tkelman after grepping around in the Homebrew source, it sounds like we just need to pass I don't think the Homebrew maintainers will want to add our servers as an "official mirror", since we can't really give them upload access and then ask them to upload these packages any time they're updated. I don't want to maintain a mirrored copy of their formulae (modulo a changed bottle
I don't think |
@timholy I feel like a rather large number of my github threads are hijackings of yours. I'm not sure if that's just because of the prodigious amount of Julia work you do, or instead because of some strange twist of fate that causes you to bump up against things I'm responsible for so often. ;) |
Since this was a PR, I think that's preferred, yes. For commits that reference a corresponding issue number so the commit is easy to find from the issue page, I also think the backport pending label is harder to lose track of than mentioning |
@staticfloat, hijack away.
"Takes one to know one" (there, now I feel like I'm back in 2nd grade). |
That's roughly what I had in mind, yeah (also libgit2 for --HEAD). Git, gcc, and cmake are also likely to be preinstalled on Travis' OSX workers, but might not be as up-to-date as we need. The Travis OSX runs start with (as a result of
|
@tkelman new issue created: JuliaCI/julia-buildbot#13 @timholy Welp, looks like my work here is done. ;) |
@timholy are you in a hurry about backporting this or can it wait until 0.3.6? |
No hurry whatsoever. If/when it does get backported, you should include 3576665 |
That sounds fine. Perhaps because I always use 0.4, I'm also OK with a few bugs being "wontfix on 0.3." But if you're willing, your plan sounds fine. |
Backported Jeff's commit, except for the parts that touched |
I noticed that
--track-allocation=user
reports allocation for a subset of files inbase/
(I'm sure--code-coverage=user
would do the same). This appears to fix the main problems; for some reason, a filemulti.jl.mem
still gets written inbase
, and I have no idea why that would happen.