-
Notifications
You must be signed in to change notification settings - Fork 4
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
Infrastructure #3
Conversation
e70790f
to
b59bdd7
Compare
Ah ok, CI is failing because we need to have newer GCC. Will update in a bit. |
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.
Looks good, apart from the nit below. r=me with that and the GCC issue fixed.
src/lib.rs
Outdated
extern crate futures; | ||
extern crate tokio_core; | ||
|
||
pub mod cli; |
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.
Let's start this off with proper separation and not include this in lib.rs
: the library shouldn't know about arg parsing. (Yes, I realize this is all scaffolding, but this is strictly code we'd remove from this file later on anyway.)
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 want to move the cli
mod into src/bin/starling.rs
, or you don't want the module to be pub
, or you want it to be in a whole new crate? It's not clear to me what you're requesting here.
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.
I really didn't make that clear at all, sorry. I think the use of cli
shouldn't be in src/lib.rs
. src/bin/starling.rs
sounds like a good place for it.
f11a332
to
5feda29
Compare
|
5feda29
to
b472213
Compare
Crap. |
Wait, I think the ICEs are just from the process getting killed in the middle of compilation. I think this is the real culprit:
|
And that is actually triggered by a |
b472213
to
4b86189
Compare
Hrm, it seems we're still ICEing:
|
@fitzgen, is this something we should talk to cargo folks about, or just something that needs a little more digging? |
We were running into an issue where The thing keeping this from landing right now, is that AFAICT those gcc ICEs are real, and I haven't been able to find a gcc version that doesn't ICE yet. This is a bit confusing to me, since earlier/other PRs with this same mozjs have all been A-OK with gcc. Digging in more. |
a45abd7
to
4138309
Compare
So I think the ICEs are an unrelated goose chase. Even without
And that's all the information that's getting spit out in the logs... And yet it works just fine locally. |
On IRC acrichto says that this might be cargo swallowing the error, perhaps because of OOM. |
Ugh. Can you try compiling with fewer threads to see if that's the case? |
4138309
to
eb4c13e
Compare
Trying with CARGO_BUILD_JOBS=4. |
8232a1a
to
9ea0c2c
Compare
9ea0c2c
to
48a0e6b
Compare
Ok, by restricting to one parallel jobs everywhere, 1/4 (so far) CI tasks finished successfully without OOMing, while 3/4 hit the travis CI time limit. Time to slowly introduce more parallel jobs again. |
bb45d3c
to
215eb44
Compare
4 parallel jobs = some are timing out; 8 parallel jobs = OOM |
215eb44
to
4eae613
Compare
6 parallel jobs is also OOMing. |
Going to just merge this, since we are planning on dealing with CI later, and other PRs build on top of this. |
Common infrastructure types we will need: an
Error
type, anOptions
builder`, CLI arg parsing.r? @tschneidereit