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 upCheck if MANIFEST.json changes as per #8587 #8601
Conversation
highfive
commented
Nov 19, 2015
|
Thanks for the pull request, and welcome! The Servo team is excited to review your changes, and you should hear from @Manishearth (or someone else) soon. |
| @@ -0,0 +1,4 @@ | |||
| #!/bin/bash | |||
| diff=$(git diff -- tests/wpt/**/MANIFEST.json) | |||
This comment has been minimized.
This comment has been minimized.
|
This doesn't actually run the manifest update command, does it? |
|
@jdm it doesn't run update. I ran the manifest update when running the tests initially to resolve the differences you pointed to the likely came from hand editing of the MANIFEST files. I committed the changes to ensure baseline is correct. Does that make sense? If it's an incorrect approach I can back out that commit. |
|
The changes here are correct, but the new script will never report any violations unless we explicitly update the manifest each time it's run. Unlike the check for |
|
@jdm OK, so would auto running the update be an additional step for this PR? If so, can you point me to the place to start looking |
|
It's a step we need to perform in the script right before checking the result of |
|
So, run all the tests? Or is there method to just update the manifest? |
|
Oh, hrm. That's a good point. @jgraham is there a way to only trigger the manifest update in isolation? |
|
|
|
Something like |
|
@jgraham Is there any reason not to use the suggestion of |
|
etc/ci/manifest_changed.sh, line 2 [r3] (raw file): Comments from the review on Reviewable.io |
|
Let's run the same for |
|
@jdm Added. Running the two commands isn't quick, just want to flag in case it's an issue in terms of test run time. |
|
Oh, one last request! We can add the new script to http://mxr.mozilla.org/servo/source/.travis.yml#13 as well for maximum coverage. |
|
(Sorry to keep changing the goalposts :) |
|
@jdm No worries! As someone coming into the project with limited understanding of how all the parts go together, it's actually been pretty useful! Extend away |
|
@bors-servo: r+ |
|
|
Check if MANIFEST.json changes as per #8587 Adds a script which checks if either of the MANIFEST.json files change in `test/wpt` in response to #8587 - Addresses currently incorrect MANIFEST.json - Adds checking script PR for saltfs to add to CI checks to follow (servo/saltfs#163) https://reviewable.io/reviews/servo/servo/8601 <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8601) <!-- Reviewable:end -->
|
|
|
@bors-servo: retry |
Check if MANIFEST.json changes as per #8587 Adds a script which checks if either of the MANIFEST.json files change in `test/wpt` in response to #8587 - Addresses currently incorrect MANIFEST.json - Adds checking script PR for saltfs to add to CI checks to follow (servo/saltfs#163) https://reviewable.io/reviews/servo/servo/8601 <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8601) <!-- Reviewable:end -->
|
|
Check if manifest file(s) changed Should be merged with servo/servo#8601 Basically uses the script added in that PR to ensure that MANIFEST.json is not changed <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/saltfs/163) <!-- Reviewable:end -->
mfeckie commentedNov 19, 2015
Adds a script which checks if either of the MANIFEST.json files change in
test/wptin response to #8587PR for saltfs to add to CI checks to follow (servo/saltfs#163)
https://reviewable.io/reviews/servo/servo/8601