| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|