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
Remove style/testing feature #17984
Remove style/testing feature #17984
Conversation
Heads up! This PR modifies the following files:
|
Gah, there's some ruletree stuff that still needs this feature. Kept it around for testing stuff, but removed the whole complexity wrt conditional compilation of properties. |
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.
That's just to avoid asserting thread stuff right? If so, it may be worth to just mock the thread state module or something...
Losing the testing of font-feature-values
is kinda unfortunate, since we don't test that right now yet...
I didn’t realize this would involve removing tests. Can we move them to |
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... I agree with @SimonSapin that losing test coverage is not great, but I think it's not a huge deal either...
But perhaps it can be moved to tests/unit/stylo
as he suggests.
@@ -148,6 +152,7 @@ fn bench_expensive_insertion(b: &mut Bencher) { | |||
#[bench] | |||
fn bench_insertion_basic_parallel(b: &mut Bencher) { | |||
let r = RuleTree::new(); | |||
thread_state::initialize(thread_state::SCRIPT); |
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 think this would also be fine with thread_state::LAYOUT
, and would be preferable.
This is all stuff well tested on the m-c side. Most of these tests are simple tests added by new contributors back when we didn't have mochitests. Runtime flag won't work, though. |
Alright. r=me with the commits squashed or reordered. It a previous push the feature was removed before its usage was removed. Now it’s removed, added back, and removed again. Reviewed 17 of 17 files at r1, 14 of 21 files at r2, 9 of 9 files at r3. Comments from Reviewable |
@bors-servo r=SimonSapin |
📌 Commit 3c9fa22 has been approved by |
Remove style/testing feature We added this because a year ago we had no reliable Gecko CI. This meant that Gecko-only properties needed to be tested *somehow*, and we solved that by making it so that for unit tests we compile all properties, not just the servo ones. This was useful back then, but I don't think we need this anymore. We have reliable Gecko CI, and all the gecko-only stuff we tested is adequately handled by the properties-database parsing mochitests. It's a bit of annoying cruft that just complicates things; we probably should remove it. r? @emilio or @SimonSapin <!-- 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/17984) <!-- Reviewable:end -->
@bors-servo r=SimonSapin push didn't happen. gah. |
📌 Commit e1fbf5a has been approved by |
Remove style/testing feature We added this because a year ago we had no reliable Gecko CI. This meant that Gecko-only properties needed to be tested *somehow*, and we solved that by making it so that for unit tests we compile all properties, not just the servo ones. This was useful back then, but I don't think we need this anymore. We have reliable Gecko CI, and all the gecko-only stuff we tested is adequately handled by the properties-database parsing mochitests. It's a bit of annoying cruft that just complicates things; we probably should remove it. r? @emilio or @SimonSapin <!-- 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/17984) <!-- Reviewable:end -->
@bors-servo r- There’s still stuff like |
@bors-servo r+ |
📌 Commit 2ebce54 has been approved by |
Remove style/testing feature We added this because a year ago we had no reliable Gecko CI. This meant that Gecko-only properties needed to be tested *somehow*, and we solved that by making it so that for unit tests we compile all properties, not just the servo ones. This was useful back then, but I don't think we need this anymore. We have reliable Gecko CI, and all the gecko-only stuff we tested is adequately handled by the properties-database parsing mochitests. It's a bit of annoying cruft that just complicates things; we probably should remove it. r? @emilio or @SimonSapin <!-- 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/17984) <!-- Reviewable:end -->
☀️ Test successful - android, arm32, arm64, linux-dev, linux-rel-css, linux-rel-wpt, mac-dev-unit, mac-rel-css1, mac-rel-css2, mac-rel-wpt1, mac-rel-wpt2, mac-rel-wpt3, mac-rel-wpt4, windows-msvc-dev |
We added this because a year ago we had no reliable Gecko CI. This meant that Gecko-only properties needed to be tested somehow, and we solved that by making it so that for unit tests we compile all properties, not just the servo ones.
This was useful back then, but I don't think we need this anymore. We have reliable Gecko CI, and all the gecko-only stuff we tested is adequately handled by the properties-database parsing mochitests. It's a bit of annoying cruft that just complicates things; we probably should remove it.
r? @emilio or @SimonSapin
This change is