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
Update Rust to 1.15.0-nightly (71c06a56a 2016-12-18) #14633
Conversation
|
@bors-servo p=17 |
|
@bors-servo r+ |
|
|
Update Rust to 1.15.0-nightly (71c06a56a 2016-12-18) <!-- Reviewable:start --> This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/14633) <!-- Reviewable:end -->
|
|
|
@bors-servo try |
|
@bors-servo r- clean |
|
@bors-servo try |
|
@bors-servo r- try- clean |
|
@bors-servo try retry |
Update Rust to 1.15.0-nightly (71c06a56a 2016-12-18) <!-- Reviewable:start --> This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/14633) <!-- Reviewable:end -->
|
|
|
So, that’s two runs with identical failures: {"status": "FAIL", "stack": null, "subtest": null, "action": "test_result", "test": "/_mozilla/css/border_radius_asymmetric_sizes_a.html", "line": 13216, "message": "/_mozilla/css/border_radius_asymmetric_sizes_a.html 327908e8e5639151bbfceb0c4a78876203042ed1\n/_mozilla/css/border_radius_asymmetric_sizes_ref.html 5a9a64f75ad410d2c74e45ceda1c9efa61203c14\nTesting 327908e8e5639151bbfceb0c4a78876203042ed1 == 5a9a64f75ad410d2c74e45ceda1c9efa61203c14", "expected": "PASS"}
{"status": "PASS", "stack": null, "subtest": null, "action": "test_result", "test": "/_mozilla/css/text_decoration_underline_subpx_a.html", "line": 16535, "message": null, "expected": "FAIL"}
{"status": "FAIL", "stack": null, "subtest": null, "action": "test_result", "test": "/_mozilla/css/word-break-keep-all-005.htm", "line": 30050, "message": "/_mozilla/css/word-break-keep-all-005.htm 553453fad4db496e2aab49f65a8af2ec63909388\n/_mozilla/css/word-break-keep-all-ref-005.htm ec3b8afcf107bfa4cd93ad6b32c9238dfec0356d\nTesting 553453fad4db496e2aab49f65a8af2ec63909388 == ec3b8afcf107bfa4cd93ad6b32c9238dfec0356d", "expected": "PASS"} |
|
I can reproduce I can reliably reproduce the Let’s try it once more to see what happens. @bors-servo try |
|
@bors-servo try retry |
Update Rust to 1.15.0-nightly (71c06a56a 2016-12-18) <!-- Reviewable:start --> This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/14633) <!-- Reviewable:end -->
Update Rust to 1.15.0-nightly (71c06a56a 2016-12-18) <!-- Reviewable:start --> This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/14633) <!-- Reviewable:end -->
|
|
|
Screenshots bellow are of The rendering of these borders in Servo is messed up, but that could be an unrelated WebRender bug. What’s more worrying to me right now is that the text became bold just by upgrading the compiler. Could it be that On Servo master, or this PR downgraded to rustc 8f02c429a 2016-12-15 (they give identical rendering): In this PR (rustc 8f02c429a 2016-12-15): In Firefox: |
|
FWIW servo/rust-freetype@c796066 fixes the bold problem for me (except for me it's the lack of bold on |
|
@bors-servo try |
Update Rust to 1.15.0-nightly (71c06a56a 2016-12-18) <!-- Reviewable:start --> This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/14633) <!-- Reviewable:end -->
|
|
|
@bors-servo r=SimonSapin,nox |
|
|
Update Rust to 1.15.0-nightly (71c06a56a 2016-12-18) <!-- Reviewable:start --> This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/14633) <!-- Reviewable:end -->
|
|
|
@jdm @Ms2ger Doesn't rust-lang/rust#37429 mean that our DOM inheritance thing might need some fixes? We used to rely on the fact that the first field is always the parent. I did update some code to use |
|
@Manishearth You used |
|
We didn't :) Like I said, I tried to get rid of the transmutes at some point, but it's changed a lot since then and I don't even remember. |
|
@eddyb I plan to do that today or tomorrow, but wasn't going to block rustup on it since the tests pass. |



This change is