Skip to content
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

Merged
merged 1 commit into from Aug 8, 2017
Merged

Conversation

Manishearth
Copy link
Member

@Manishearth Manishearth commented Aug 6, 2017

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 Reviewable

@highfive
Copy link

highfive commented Aug 6, 2017

Heads up! This PR modifies the following files:

  • @bholley: components/style/properties/longhand/position.mako.rs, components/style/Cargo.toml, components/style/properties/data.py, components/style/properties/shorthand/text.mako.rs, components/style/properties/build.py and 6 more
  • @canaltinova: components/style/properties/longhand/position.mako.rs, components/style/Cargo.toml, components/style/properties/data.py, components/style/properties/shorthand/text.mako.rs, components/style/properties/build.py and 6 more
  • @wafflespeanut: python/servo/testing_commands.py
  • @emilio: components/style/properties/longhand/position.mako.rs, components/style/Cargo.toml, components/style/properties/data.py, components/style/properties/shorthand/text.mako.rs, ports/geckolib/Cargo.toml and 7 more

@highfive highfive added the S-awaiting-review There is new code that needs to be reviewed. label Aug 6, 2017
@Manishearth
Copy link
Member Author

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.

Copy link
Member

@emilio emilio left a 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...

@SimonSapin
Copy link
Member

I didn’t realize this would involve removing tests. Can we move them to tests/units/stylo instead? Or have a runtime flag instead of a compilation flag?

Copy link
Member

@emilio emilio left a 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);
Copy link
Member

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.

@Manishearth
Copy link
Member Author

I didn’t realize this would involve removing tests.

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.

@SimonSapin
Copy link
Member

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.
Review status: all files reviewed at latest revision, 1 unresolved discussion.


Comments from Reviewable

@emilio emilio removed the S-awaiting-review There is new code that needs to be reviewed. label Aug 7, 2017
@Manishearth
Copy link
Member Author

@bors-servo r=SimonSapin

@bors-servo
Copy link
Contributor

📌 Commit 3c9fa22 has been approved by SimonSapin

@highfive highfive assigned SimonSapin and unassigned emilio Aug 7, 2017
@highfive highfive added the S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. label Aug 7, 2017
@bors-servo
Copy link
Contributor

⌛ Testing commit 3c9fa22 with merge c2299e3...

bors-servo pushed a commit that referenced this pull request Aug 7, 2017
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 -->
@highfive highfive added S-awaiting-review There is new code that needs to be reviewed. and removed S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. labels Aug 7, 2017
@Manishearth
Copy link
Member Author

@bors-servo r=SimonSapin

push didn't happen. gah.

@bors-servo
Copy link
Contributor

📌 Commit e1fbf5a has been approved by SimonSapin

@highfive highfive added S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. and removed S-awaiting-review There is new code that needs to be reviewed. labels Aug 7, 2017
@bors-servo
Copy link
Contributor

⌛ Testing commit e1fbf5a with merge 41fc0d8...

bors-servo pushed a commit that referenced this pull request Aug 7, 2017
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 -->
@SimonSapin
Copy link
Member

@bors-servo r-

There’s still stuff like cfg!(feature = "testing") being added in the second commit. Maybe easier to squash everything?

@highfive highfive added S-awaiting-review There is new code that needs to be reviewed. and removed S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. labels Aug 7, 2017
@SimonSapin
Copy link
Member

@bors-servo r+

@bors-servo
Copy link
Contributor

📌 Commit 2ebce54 has been approved by SimonSapin

@highfive highfive added S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. and removed S-awaiting-review There is new code that needs to be reviewed. labels Aug 8, 2017
@bors-servo
Copy link
Contributor

⌛ Testing commit 2ebce54 with merge 32f8352...

bors-servo pushed a commit that referenced this pull request Aug 8, 2017
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
Copy link
Contributor

☀️ 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
Approved by: SimonSapin
Pushing 32f8352 to master...

@bors-servo bors-servo merged commit 2ebce54 into servo:master Aug 8, 2017
@highfive highfive removed the S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. label Aug 8, 2017
@Manishearth Manishearth deleted the rm-testing branch May 7, 2019 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants