| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
| |
We now use rust-lang.org nightly builds rather than our own snapshots.
|
| |
|
|
|
|
|
|
| |
Urg! The Chromium HSTS preload JSON file contains single line comments. Previously these were filtered out with a very simple regex that just looked for '//' and removed the line. Now the file has added a couple fields that have URLs in them that were erroneously removed and caused the JSON parsing to fail. This commit slightly complicates the regex to fix this specific problem.
If this happens again, it's likely worth it to figure out how to use a real parser to remove the comments.
servo/servo#8760
|
| |
|
|
| |
of the Rust documentation.
|
| |
|
|
| |
… and libc 0.2 and many other dependencies
|
| |
|
|
|
| |
'e' is also used later on in a list comprehension, and flake8 warns when
variables get redefined within a function
|
| |
|
|
|
| |
* Lots of rust-isms
* Mutable iterator for modifying entries (much better)
|
| |
|
|
|
| |
* No longer download the HSTS list as a bootstrap step
* Check the current revision of the HSTS list into source
|
| | |
|
| |
|
|
|
| |
This resolves the first part of servo/servo#6105. The remaining part is
to update the list based on the STS headers from the server.
|
| |
|
|
|
|
|
| |
Fixes #6236
Also included in this commit are the changes need to make flake8 pass
for the existing python file
|
| | |
|
| |
|
|
|
|
|
| |
Versions of git before 1.8.1 do not support git submodule --recursive sync
This commit makes update_submodules() exit with an error message if the version is <1.8.1
https://github.com/servo/servo/issues/5637
|
| |
|
|
| |
The urllib version used a `FancyURLOpener` which use urllib. But urllib does not not handle proxies with SSL well.
A better solution would be to use `requests` but I prefer to stay with the "no-dependency" approach.
|
| | |
|
| |
|
|
| |
based on sys.stdout.isatty() (Issue #5043).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bootstrapping automatically downloads new Rust and Cargo snapshots
as needed into versioned directories,
but do not remove now-unused versions.
This is the desired behavior for `git bisect` to be usable.
However, this means that old version keep accumulating, taking up disk space.
This adds a mach command to remove snapshots other than the ones
currently being used.
It is never run automatically.
To be safe, the command defaults to only printing what would be removed,
and only removes stuff when run with a `-f` argument.
|
| | |
|
| |\
| |
| |
| | |
This is @acmiyaguchi's already-reviewed patch from #3388, rebased and squashed onto servo master. Fixes #3353.
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
| |
Also hints that 32bit snapshots are unavailable on failure
Resolves #3739
fixup! Panic when bootstrap downloads fail
|
| |
|
|
| |
non-optimized, debug build of mozjs and rust-mozjs. Update the Cargo snapshot to enable new feature support.
|
| | |
|
| |
|
|
| |
Relevant to #3580.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
That way, whenever rust-snapshot-hash changes, mach will look for
the Rust snapshot in a different directory and re-boostrap as needed.
However, older rust version will be left behind never cleaned up.
This is good for git-bisect, but not for disk space:
the current snapshot is 618 MB.
In the future, we may want `mach clean` or some other comment
to remove unused Rust snapshots.
CC #3388
|
| |
|
|
| |
(My editor screams at me for flake8 lint errors.)
|
| |
|
|
|
|
|
|
|
|
|
| |
Dumb terminals can only interpret a limited number of control codes,
and rewriting the terminal buffer will make `./mach build` very talkative
on these terminals.
This can be tested by setting the environment variable TERM to "dumb"
as such:
TERM=dumb ./mach build
|
| |
|
