| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
web-platform-tests.
This reverts commit c315404db80c92a695531b0aa4bcf61c125a3bff, reversing
changes made to b00583bd4e7169a6b952633df718268904f2bd0c.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prior to this commit:
* Our Python dependency story was a bit of a mess. We had complete
Python packages (wheels and directories) living in-tree, despite
not having any changes from upstream. This is particularly bad because
`setup.py` never gets run on these packages which could (sometimes
silently) unintended breakage.
* Python virtual environments (virtualenv) were only utilized for
testing web-platform tests
After this commit:
* A single virtualenv (`python/_virtualenv`) is activated upon *every*
call to mach
* A requirements file (`python/requirements.txt`) is added to describe
the dependencies needed by Python modules in `python/`. The child
commit immediately following this will remove all the dependencies
no longer needed in-tree (for the sake of keeping this commit
readable).
Relevant to https://github.com/servo/servo/issues/861
Fixes https://github.com/servo/servo/issues/6999
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Make mach test work with wpt tests.
Allow specifying specific testsuites on the command line
Allow specifying paths to CSS tests on the command line
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This speeds up `./mach build --dev` followed by `./mach build-cef` by
25%. When rust-lang/cargo#497 is fixed, this speedup will increase
dramatically.
<!-- Reviewable:start -->
[<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/6306)
<!-- Reviewable:end -->
|
| |
| |
| |
| |
| | |
This speeds up `./mach build --dev` followed by `./mach build-cef` by a
large amount, and also speeds up other build combos found in our CI.
|
|/
|
|
| |
'mach test' to be able to select the render-mode.
|
|
|
|
|
|
|
| |
Fixes #6236
Also included in this commit are the changes need to make flake8 pass
for the existing python file
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Closes #5707. (Includes a rebase of it.)
Fixes #5688.
|
| |
|
| |
|
|
|
|
|
|
|
| |
All unit tests will move there, and it should be much faster to build
than every other crate together.
Fix #5291.
|
|
|
|
|
| |
This changes the `mach test-unit -p foo` command to build only the requested
crate, not the entire `servo` crate.
|
|
|
|
|
|
| |
For consistency with Cargo params, and related mach commands like
`mach update-cargo`. The `-c` version is still available as an alias for
compatibility with old scripts.
|
| |
|
|
|
|
| |
These are run through the same harness as the web-platform-tests.
|
|
|
|
|
|
| |
wptrunner.
Also remove the shell script and ensure that default options are set in a single location
|
| |
|
| |
|
|\
| |
| |
| | |
`./mach test tests/wpt/web-platform-tests/html/browsers/history/the-location-interface/security_location_0.sub.htm` is still failing with the same message as reported in #3219.
|
| | |
|
|/ |
|
|\
| |
| |
| | |
fixes #5046
|
| | |
|
|/ |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
This is a quick and dirty workaround for issue #3928. Basically, `cargo test` is deleting `./target/servo`, which is clearly not ideal if we want to do anything with servo after running the unit tests. This PR makes sure to rebuild after running `./mach test-unit`.
I'm not familiar enough with cargo yet to know why it's doing this or what better alternatives there are to fixing this. Having to rebuild afterwards feels pretty ugly to me, but my rationalization right now is that the time it takes to build is negligible in comparison to the time it takes to run the tests. Ideally, this should be something we could take care of in Cargo.toml, but again, I'm new to this (and the documentation seems less than helpful from what I can tell so far).
I won't be available for the rest of the day, so if anyone has suggestions, or wants to wait for a better solution, I'll get back to it tomorrow probably. Otherwise, this PR at least makes `./mach test` work properly, so there's that.
|
| | |
|
| |
| |
| |
| | |
(ugly) workaround for issue #3928
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When running commands through Registrar.dispatch, mach does not behave
in the same way it would as if it were running through the command line.
Defaults normally provided through a combination of @CommandArgument and
argparse magic are ignored.
I have some ideas as to how to fix this, but until then, this will allow
`./mach test` to run through test-unit properly.
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Example usage:
`./mach test-unit -c style`
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Example usage:
`./mach test-unit -c style`
|
| | |
| | |
| | |
| | | |
...so that PyLint stops yelling at me
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| | |
There are none, but the contenttest program fails with:
```
task '<main>' panicked at 'Required option 'source-dir' missing.', ../../tests/contenttest.rs:48
```
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Minor change, added unit test filter to components so that ./mach test-unit [test-filter] works in line with documentation.
I'd personally like to also make filters on the components as well as the tests. This would change the interface (probably to ./mach test-unit [component-filter] [test-filter]), but change is NOT in this pull request.
|
| | | |
|
|/ /
| |
| |
| |
| | |
No actual change in functionality here. I was just unhappy with the way
test-ref was singled out before, and realized an obvious fix.
|
| |
| |
| |
| |
| | |
In addition, `./mach test` will now take advantage of this when
inferring test suites from test files.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Usage Example:
```
$ ./mach test tests/wpt/web-platform-tests/dom/interfaces.html
0:00.27 LOG: MainThread INFO Using 1 client processes
...
```
Note that while there is no functionality for `test-ref` to accept
individual files, `./mach test tests/ref` will still trigger `test-ref`.
|