about summary refs log tree commit diff
path: root/src/libtest/lib.rs
AgeCommit message (Collapse)AuthorLines
2019-05-20Rollup merge of #60895 - chandde:master, r=alexcrichtonMazdak Farrokhzad-4/+5
Enable thumbv7a-pc-windows-msvc target build end to end in rust/master With this PR, plus another commit https://github.com/rust-lang-nursery/compiler-builtins/commit/cf98161da7ed5217b6031796f0f60b4dd07148a4, I'm able to build the target thumbv7a-pc-windows-msvc successfully, and I'm able to use the stage2 artifacts to build arm32 projects. The commit in compiler_builtins is in release 0.1.14, the current cargo.lock in rust master still uses 0.1.12, so I bumped the compiler_builtins version in cargo.lock to 0.1.15 The command I used to build rust ``` c:\python27\python.exe x.py build --host x86_64-pc-windows-msvc --build x86_64-pc-windows-msvc --target thumbv7a-pc-windows-msvc --verbose ``` **Changes** 1. update cargolock to use compiler_builtins 0.1.15 2. handle libunwind in libtest for thumv7a the same as what we have for aarch64 3. in llvm codegen add a field in CodegenContext to carry the arch, so later in create_msvc_imps function, the arch can be used to check against "x86", instead of 32 pointer width. Apparently Thumv7a is handled differently than x86. **Background** I'm from Microsoft working on enabling Azure IoTEdge on ARM32 Windows IoTCore, Azure IoTEdge has a component called IoTEdged written in rust as a NT service running on Windows, so we need to enable rust on thumbv7a in order to have full IoTEdge. My colleague had made some heavy lifting and we've been using our private toolchain to build IoTEdged in our devops pipeline, because at that time we cannot build thumbv7a target end to end successfully. This change is a followup to enable the end to end build for thumbv7a-pc-windows-msvc target. **Next step** I'll submit more changes to have this target built nightly in rust/master, to achieve the same availability for aarch64-pc-windows-msvc, indexed here https://rust-lang.github.io/rustup-components-history/aarch64-pc-windows-msvc.html and can be manually installed. **Please do share what takes to make this happen, is there a formal process I need to follow\?**
2019-05-18fix line lengthchandde-3/+4
2019-05-17optimize the arm64 OR arm32 checkchandde-1/+1
2019-05-14Update lib.rschandde-3/+3
2019-05-13Remove bitrig support from rustMarcel Hellwig-1/+0
2019-04-07Revert "Auto merge of #57842 - gnzlbg:extract_libtest, r=gnzlbg"Jacob Greenfield-26/+2202
This reverts commit 3eb4890dfe6db0279fdd3cda19f9643873ae3db9, reversing changes made to 7a4df3b53da369110984a2b57419c05a53e33b38.
2019-03-25Moves test::black_box to core::hintgnzlbg-17/+1
This changes removes a cyclic dependency between the "test" and "libtest" crates, where "libtest" depends on "test" for "black_box", but "test" depends on "libtest" for everything else. I've chosen the "hint" module because there seems to be enough consensus in the discussion of RFC2360 that this module is where such an intrinsic would belong, but this PR does not implement that RFC! (note: if that RFC ever gets merged, the API, docs, etc. of this API will need to change). For backwards compatibility reasons I've chosen to also keep the "test" feature gate for these instead of adding a new feature gate. If we change the feature gate, we'll potentially all benchmarks, and while that's something that we could do, it seems unnecessary to do that now - if RFC2360 gets merged, we'll need to do that anyways.
2019-03-20Move some bench tests back from libtestgnzlbg-0/+25
2019-03-19Export stats::Summary from libtestgnzlbg-1/+4
2019-03-19Add missing explicit importsgnzlbg-1/+6
2019-03-19Move black_box back to rust-lang/libtest and use explicit importsgnzlbg-1/+20
2019-03-19Allow the staged_apignzlbg-0/+1
2019-03-19Use feature(test)gnzlbg-0/+1
2019-03-19Re-export libtestgnzlbg-0/+17
2019-03-19Move libtest out of rust-lang/rustgnzlbg-2247/+0
2019-02-24Simplify exclude_should_panic flag.memoryruins-12/+6
2019-02-23Add unstable option to ignore should_panic tests.memoryruins-0/+45
2019-02-14Rollup merge of #57856 - lzutao:fix-old-first-edition, r=steveklabnikMazdak Farrokhzad-1/+1
Convert old first edition links to current edition one r? @steveklabnik
2019-02-13Convert old doc links to current editionLzu Tao-1/+1
Use footnote style to bypass the tidy check
2019-02-10libs: doc commentsAlexander Regueiro-1/+1
2019-02-07Remove images' url to make it work even without internet connectionGuillaume Gomez-6/+1
2019-02-04Excute rustfmt for fixing tidy checkHirokazu Hata-55/+86
2019-02-04Transition libtest to 2018 editionHirokazu Hata-16/+17
2019-01-27Auto merge of #57765 - Mark-Simulacrum:bootstrap-bump, r=alexcrichtonbors-1/+0
Bump bootstrap compiler to 1.33 beta r? @alexcrichton or @pietroalbini cc @rust-lang/release
2019-01-26Bump bootstrap compiler to 1.33 betaMark Rousskov-1/+0
2019-01-20Add missing #![feature(rustc_private)] annotationIgor Matuszewski-1/+1
2019-01-14Stabilize `cfg_target_vendor`, #29718Jethro Beekman-1/+1
2018-12-31Bound sgx target_env with fortanix as target_vendorYu Ding-2/+4
Signed-off-by: Yu Ding <dingelish@gmail.com>
2018-12-25Remove licensesMark Rousskov-10/+0
2018-12-11Auto merge of #56243 - RalfJung:test-deterministic, r=alexcrichtonbors-15/+27
libtest: Use deterministic HashMap, avoid spawning thread if there is no concurrency It seems desirable to make a test and bench runner deterministic, which this achieves by using a deterministic hasher. Also, we we only have 1 thread, we don't bother spawning one and just use the main thread. The motivation for this is to be able to run the test harness in miri, where we can neither access the OS RNG, nor spawn threads.
2018-12-11use an enum instead of boolRalf Jung-12/+17
2018-12-07Various minor/cosmetic improvements to codeAlexander Regueiro-4/+4
2018-12-07Add x86_64-fortanix-unknown-sgx target to libstd and dependenciesJethro Beekman-4/+6
The files src/libstd/sys/sgx/*.rs are mostly copied/adapted from the wasm target. This also updates the dlmalloc submodule to the very latest version.
2018-11-27fix libtest test suiteRalf Jung-6/+6
2018-11-27Do not spawn a thread if we do not use concurrencyRalf Jung-5/+8
2018-11-27use deterministic HashMap in libtestRalf Jung-4/+8
2018-10-14add option to libtest to run all testsEmerentius-46/+104
flag name is --include-ignored requires -Zunstable-options for now
2018-10-14refactor filter_testsEmerentius-43/+23
same behaviour, just shorter
2018-09-27Bump to 1.31.0 and bootstrap from 1.30 betaJosh Stone-1/+1
2018-09-24aarch64-pc-windows-msvc: Don't link libpanic_unwind to libtest.Michael Woerister-1/+9
2018-09-15Revert "Auto merge of #53527 - Emerentius:test_all, r=nrc"Eduard-Mihai Burtescu-119/+81
This reverts commit 9f53c87b4b1f097e111c9525d60470ed22631018, reversing changes made to cba0fdf43c22795822e1d7c751a69e6c85007221.
2018-09-15Auto merge of #53527 - Emerentius:test_all, r=nrcbors-81/+119
Add option to run all tests This adds the "--include-ignored" flag to libtest, which allows running ignored and unignored tests in one go. Closes #50363
2018-09-11stabalize infer outlives requirements (RFC 2093).toidiu-1/+0
Co-authored-by: nikomatsakis
2018-09-05rename option to run all tests and make it unstableEmerentius-12/+20
new name: --include-ignored requires -Zunstable-options
2018-09-04Introduce Custom Test FrameworksJohn Renner-1/+2
2018-08-29Replace usages of 'bad_style' with 'nonstandard_style'.Corey Farwell-1/+1
`bad_style` is being deprecated in favor of `nonstandard_style`: - https://github.com/rust-lang/rust/issues/41646
2018-08-24check that adding infer-outlives requirement to all crates worksNiko Matsakis-0/+1
2018-08-20add option to run all testsEmerentius-46/+96
add --all flag to libtest that runs ignored and not ignored tests
2018-08-20refactor filter_testsEmerentius-43/+23
same behaviour, just shorter
2018-08-15Rollup merge of #52453 - srijs:fix-52436, r=TimNNGuillaume Gomez-1/+8
improve diagnostics for tests with custom return values This is an attempt at getting the ball rolling to improve the diagnostics for test functions that return custom `impl Termination` values (see #52436). An alternative could be to use `eprintln!`, but including this in the panic message felt nicely consistent with how failing test assertions would be reported. Let me know what you think!
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-24 21:06:39 +0000