Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upscript: Make timer events e10s-safe. #8237
Conversation
|
Until this lands e10s cannot land. |
|
Review status: 0 of 13 files reviewed at latest revision, 1 unresolved discussion, all commit checks successful. components/script/dom/dedicatedworkerglobalscope.rs, line 232 [r1] (raw file): Comments from the review on Reviewable.io |
|
This should not change the lifetime of workers from the status quo (which will, in fact, leak until the ActiveTimers value is dropped). Addressing that issue should happen separately. |
|
@bors-servo: r+ |
|
|
script: Make timer events e10s-safe. Closes #8235. r? @jdm <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8237) <!-- Reviewable:end -->
|
|
|
|
@bors-servo: r=jdm |
|
|
script: Make timer events e10s-safe. Closes #8235. r? @jdm <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8237) <!-- Reviewable:end -->
|
|
|
No idea what the error means. @larsbergstrom ? |
|
Plausibly the gonk Cargo.lock isn't up to date, so it ends up pulling in the latest version of something that isn't specified? |
|
Isn't tidy supposed to catch that, or do we not run that check on gonk? |
|
Tidy only looks for incompatible entries in single lock files; there is no inter-file comparison. |
|
I just checked and the lock files are fine on master, and I can't see why this PR would affect that since no toml files are modified, however :( |
|
Oh wait, there are Cargo.lock file changes only for gonk that upgrade serde, which presumably is incompatible with the version of rustc we're currently using. |
|
@jdm I meant that if the lockfile after build is different than the lockfile it started with. That is supposed to catch out of date Cargo.locks |
|
Pretty sure that check wouldn't be reached if the build failed... |
|
|
pcwalton commentedOct 28, 2015
Closes #8235.
r? @jdm