| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2020-07-28 | reenable tests after moving std | mark | -3/+1 | |
| 2020-07-28 | Fix bad rebase | Joshua Nelson | -1/+1 | |
| 2020-07-27 | Add tests for the new behavior | Joshua Nelson | -3/+92 | |
| - Only set stage 2 in dist tests - Add test for `x.py doc` without args - Add test for `x.py build` without args - Add test for `x.py build --stage 0` | ||||
| 2020-07-27 | Move tests into a submodule | Joshua Nelson | -461/+470 | |
| 2020-07-27 | Fix most bootstrap tests | Joshua Nelson | -1/+2 | |
| Uses --stage 2 for all the existing tests | ||||
| 2020-07-27 | mv std libs to library/ | mark | -3/+5 | |
| 2020-07-17 | Teach bootstrap about target files vs target triples | Jake Goulding | -28/+28 | |
| `rustc` allows passing in predefined target triples as well as JSON target specification files. This change allows bootstrap to have the first inkling about those differences. This allows building a cross-compiler for an out-of-tree architecture (even though that compiler won't work for other reasons). Even if no one ever uses this functionality, I think the newtype around the `Interned<String>` improves the readability of the code. | ||||
| 2020-07-01 | Tests for number of times rustdoc is built with x.py test and doc. | Eric Huss | -0/+79 | |
| 2020-02-03 | bootstrap: fix clippy warnings | Matthias Krüger | -1/+0 | |
| 2019-12-22 | Format the world | Mark Rousskov | -298/+81 | |
| 2019-12-11 | Fix a test in the bootstrap test suite | Alex Crichton | -0/+4 | |
| 2019-08-23 | bootstrap: Merge the libtest build step with libstd | Alex Crichton | -89/+64 | |
| Since its inception rustbuild has always worked in three stages: one for libstd, one for libtest, and one for rustc. These three stages were architected around crates.io dependencies, where rustc wants to depend on crates.io crates but said crates don't explicitly depend on libstd, requiring a sysroot assembly step in the middle. This same logic was applied for libtest where libtest wants to depend on crates.io crates (`getopts`) but `getopts` didn't say that it depended on std, so it needed `std` built ahead of time. Lots of time has passed since the inception of rustbuild, however, and we've since gotten to the point where even `std` itself is depending on crates.io crates (albeit with some wonky configuration). This commit applies the same logic to the two dependencies that the `test` crate pulls in from crates.io, `getopts` and `unicode-width`. Over the many years since rustbuild's inception `unicode-width` was the only dependency picked up by the `test` crate, so the extra configuration necessary to get crates building in this crate graph is unlikely to be too much of a burden on developers. After this patch it means that there are now only two build phasese of rustbuild, one for libstd and one for rustc. The libtest/libproc_macro build phase is all lumped into one now with `std`. This was originally motivated by rust-lang/cargo#7216 where Cargo was having to deal with synthesizing dependency edges but this commit makes them explicit in this repository. | ||||
| 2019-07-27 | Remove run-pass test suites | Vadim Petrochenkov | -4/+1 | |
| 2019-06-24 | bootstrap: pass '--pass' on to compiletest. | Mazdak Farrokhzad | -0/+2 | |
| 2019-06-16 | Separate bootstrap module | chansuke | -0/+656 | |
