rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2023-01-11	Move /src/test to /tests	Albert Larsan	-68/+0

2022-10-28	libtest: run all tests in their own thread, if supported by the host	Ralf Jung	-3/+3

2022-08-23	Diagnose missing includes in run-make tests	Tomasz Miąsko	-1/+1

2022-03-11	Add tests for JSON and console output	Mark Rousskov	-4/+4

2022-01-28	remove allow_fail test flag	yuhaixin.hx	-2/+2

2020-11-29	libtest: Make `sed` arguments compatible with apple	Jakob Schikowski	-2/+2

2020-11-27	libtest: Print the total time taken to execute a test suite	Jakob Schikowski	-5/+5

2020-01-12	Update `output-default.json` and rustdoc test	varkor	-2/+2

2019-07-12	libtest: support display_output in JSON formatter	Paul Emmerich	-6/+21

2019-06-05	Reblessed tests.	Alexander Regueiro	-1/+1

2019-04-22	Remove double trailing newlines	varkor	-1/+0

2018-12-25	Remove licenses	Mark Rousskov	-21/+1

2018-12-13	Update panic message to be clearer about env-vars	Daniel Silverstone	-1/+1
	Esteban Kuber requested that the panic message make it clear that `RUST_BACKTRACE=1` is an environment variable. This change makes that clear. Wording provided in part by David Tolnay.
2018-11-27	fix run-make-fulldeps/libtest-json	Ralf Jung	-1/+1

2018-08-31	Fix tests for json formatting	Charlie Andrews	-2/+2

2018-05-05	Fix libtest-json test	John Kåre Alsaker	-1/+1

2018-03-22	rustc: Add a `#[wasm_custom_section]` attribute	Alex Crichton	-0/+74
	This commit is an implementation of adding custom sections to wasm artifacts in rustc. The intention here is to expose the ability of the wasm binary format to contain custom sections with arbitrary user-defined data. Currently neither our version of LLVM nor LLD supports this so the implementation is currently custom to rustc itself. The implementation here is to attach a `#[wasm_custom_section = "foo"]` attribute to any `const` which has a type like `[u8; N]`. Other types of constants aren't supported yet but may be added one day! This should hopefully be enough to get off the ground with some custom section support. The current semantics are that any constant tagged with `#[wasm_custom_section]` section will be appended to the corresponding section in the final output wasm artifact (and this affects dependencies linked in as well, not just the final crate). This means that whatever is interpreting the contents must be able to interpret binary-concatenated sections (or each constant needs to be in its own custom section). To test this change the existing `run-make` test suite was moved to a `run-make-fulldeps` folder and a new `run-make` test suite was added which applies to all targets by default. This test suite currently only has one test which only runs for the wasm target (using a node.js script to use `WebAssembly` in JS to parse the wasm output).