about summary refs log tree commit diff
path: root/src/tools/compiletest
AgeCommit message (Collapse)AuthorLines
2019-11-03Validate error patterns and error annotation in ui tests when presentTomasz Miąsko-8/+11
Previously, when compilation succeeded, neither error patterns nor error annotation would be validated. Additionally, when compilation failed, only error patterns would be validated if both error patterns and error annotation were present. Now both error patterns and error annotation are validated when present, regardless of compilation status. Furthermore, for test that should run, the error patterns are matched against executable output, which is what some of tests already expect to happen, and when #65506 is merged even more ui tests will.
2019-10-25Re-enable Emscripten's exception handling supportThomas Lively-4/+0
Passes LLVM codegen and Emscripten link-time flags for exception handling if and only if the panic strategy is `unwind`. Sets the default panic strategy for Emscripten targets to `unwind`. Re-enables tests that depend on unwinding support for Emscripten, including `should_panic` tests.
2019-10-16Upgrade Emscripten targets to use upstream LLVM backendThomas Lively-1/+4
- Compatible with Emscripten 1.38.46-upstream or later upstream. - Refactors the Emscripten target spec to share code with other wasm targets. - Replaces the old incorrect wasm32 C call ABI with the correct one, preserving the old one as wasm32_bindgen_compat for wasm-bindgen compatibility. - Updates the varargs ABI used by Emscripten and deletes the old one. - Removes the obsolete wasm32-experimental-emscripten target. - Uses EMCC_CFLAGS on CI to avoid the timeout problems with #63649.
2019-10-05Revert "Auto merge of #63649 - tlively:emscripten-upstream-upgrade, ↵Tyler Mandry-4/+1
r=alexcrichton" This reverts commit 7870050796e5904a0fc85ecbe6fa6dde1cfe0c91, reversing changes made to 2e7244807a7878f6eca3eb7d97ae9b413aa49014.
2019-10-04Fix ABI, run and fix more tests, re-enable CI for PRsThomas Lively-1/+4
2019-09-28Support run-fail ui testsTyler Mandry-4/+25
2019-09-26Upgrade env_logger to 0.7Mateusz Mikuła-1/+1
2019-09-23Add `#![deny(warnings)]` to internal toolsAlex Crichton-0/+1
2019-09-15use println!()Guanqun Lu-4/+4
2019-09-07run-pass tests shouldn't have unused contentsMark Rousskov-1/+10
2019-09-07Rollup merge of #64258 - smaeul:patch/arm-tests, r=Mark-SimulacrumMazdak Farrokhzad-3/+7
compiletest: Match suffixed environments This fixes a case where an `ignore-musl` test was not ignored on `armv7-unknown-linux-musleabihf` because the environment did not exactly match. Only enforce that the environment starts with the argument to `ignore-`.
2019-09-07Rollup merge of #64235 - mati865:env_logger, r=alexcrichtonMazdak Farrokhzad-1/+1
Upgrade env_logger to 0.6
2019-09-07compiletest: Match suffixed environmentsSamuel Holland-3/+7
This fixes a case where an `ignore-musl` test was not ignored on `armv7-unknown-linux-musleabihf` because the environment did not exactly match. Only enforce that the environment starts with the argument to `ignore-`.
2019-09-06Upgrade env_logger to 0.6Mateusz Mikuła-1/+1
2019-09-05Merge pull request #17 from rust-lang/masterBaoshan-23/+93
sync with rust-lang/rust master branch
2019-09-05simplify is_vxworks_pure_dynamicBaoshan Pang-8/+1
2019-09-04Merge pull request #15 from Wind-River/bpang-runtestBaoshan-2/+2
change RUST_TEST_DYLINK to RUST_VXWORKS_TEST_DYLINK
2019-09-04Auto merge of #63825 - nathanwhit:check-run-results, r=Mark-Simulacrumbors-23/+93
Allow checking of run-pass execution output in compiletest Closes #63751 Adds a `check-run-results` flag to compiletest headers, which if enabled checks the output of the execution of a run-pass test's binary against expected output.
2019-09-03change RUST_TEST_DYLINK to RUST_VXWORKS_TEST_DYLINKBaoshan Pang-2/+2
2019-09-03Merge pull request #12 from rust-lang/masterBaoshan-7/+3
sync with rust-lang/rust branch master
2019-09-03Strip remote-test-client output from run stdoutnathanwhit-2/+18
The remote-test-client outputs a message of the form "uploaded "<build_dir>/<executable_path>", waiting for result" onto stdout when executing a test, which is then captured in the process result. This needs to be removed when comparing the results of the run-pass test execution.
2019-09-03Rollup merge of #64071 - guanqun:style-fix, r=CentrilMazdak Farrokhzad-2/+2
use just one name when parameters and fields are the same
2019-09-02Ignore check-run-results tests for wasm32-barenathanwhit-0/+5
Ignores run-pass tests with the `check-run-results` flag enabled for the wasm32-bare ("wasm32-unknown-unknown") target, as it does not support printing to stdout/stderr.
2019-09-02following the same styleGuanqun Lu-2/+2
2019-09-01remove the unstable rustdoc parameter --linkerAndreas Jonson-5/+1
use the code generation parameter -Clinker (same parameter as rustc) to control what linker to use for building the rustdoc test executables. closes: #63816
2019-08-27run test for vxWorks in 'pure' static linking mode by default;Baoshan Pang-2/+27
if environment variables 'RUST_TEST_DYLINK' is set to 1, then run test in 'pure' dynamic linking mode
2019-08-25Allow checking of both compile & run output for run-pass testsNathan-18/+34
2019-08-22Compare run-pass outputs if `check-run-results` flag enabledNathan-2/+19
Addresses #63751
2019-08-22Extract loading and comparison of compiletest outputs to new fnNathan-15/+20
Moved into ```fn load_compare_outputs(&self, proc_res: &ProcRes, explicit_format: bool) -> usize```
2019-08-22Add header flag to check run-pass test outputnathanwhit-0/+11
2019-08-131. support crt-staticBaoshan Pang-3/+3
2. change armv7_wrs_vxworks to armv7_wrs_vxworks_eabihf. 3. use wr-** instead of vx-** 4. set PIE to false 5. code cleanup
2019-08-02compiletest: Unconfigure tests during normal buildVadim Petrochenkov-173/+183
2019-07-28Remove lint annotations in specific crates that are already enforced by ↵Vadim Petrochenkov-1/+0
rustbuild Remove some random unnecessary lint `allow`s
2019-07-27Remove run-pass test suitesVadim Petrochenkov-18/+11
2019-07-22tests: Require run-pass tests without annotations to run successfully againVadim Petrochenkov-1/+3
2019-07-16Add supporting for vxWorksBaoshan Pang-0/+13
r? @alexcrichton
2019-07-06Remove compile-pass from compiletestYuki Okushi-3/+0
Also change annotations in some tests
2019-06-26Hash force_pass_mode when config.mode == Pretty.Mazdak Farrokhzad-1/+1
2019-06-24Address review comments.Mazdak Farrokhzad-23/+20
2019-06-24compiletest: support '--pass check' and '// ignore-pass'.Mazdak Farrokhzad-22/+89
2019-06-16compiletest: Move pass mode update into a separate functionVadim Petrochenkov-32/+36
2019-06-16compiletest: Remove `skip-codegen`Vadim Petrochenkov-5/+1
2019-06-16compiletest: Validate pass modes harderVadim Petrochenkov-7/+34
2019-06-16compiletest: Introduce `// {check,build,run}-pass` pass modesVadim Petrochenkov-48/+31
2019-05-20Address CDB review feedbackMaulingMonkey-32/+26
- Don't add path_buf_capacity feature. - Convert `find_cdb` to early return style, reducing indentation - Simplify `compute_stamp_hash` for CDB to just hash it's path, if any.
2019-05-20Fix CDB support tidy check line length failures.MaulingMonkey-5/+6
2019-05-19Add basic CDB support to debuginfo compiletest s, to help catch `*.natvis` ↵MaulingMonkey-23/+190
regressions, like those fixed in #60687. Several Microsoft debuggers (VS, VS Code, WinDbg, CDB, ...) consume the `*.natvis` files we embed into rust `*.pdb` files. While this only tests CDB, that test coverage should help for all of them. CHANGES src\bootstrap - test.rs: Run CDB debuginfo tests on MSVC targets src\test\debuginfo - issue-13213.rs: CDB has trouble with this, skip for now (newly discovered regression?) - pretty-std.rs: Was ignored, re-enable for CDB only to start with, add CDB tests. - should-fail.rs: Add CDB tests. src\tools\compiletest: - Added "-cdb" option - Added Mode::DebugInfoCdb ("debuginfo-cdb") - Added run_debuginfo_cdb_test[_no_opt] - Renamed Mode::DebugInfoBoth -> DebugInfoGdbLldb ("debuginfo-gdb+lldb") since it's no longer clear what "Both" means. - Find CDB at the default Win10 SDK install path "C:\Program Files (x86)\Windows Kits\10\Debugger\*\cdb.exe" - Ignore CDB tests if CDB not found. ISSUES - `compute_stamp_hash`: not sure if there's any point in hashing `%ProgramFiles(x86)%` - `OsString` lacks any `*.natvis` entries (would be nice to add in a followup changelist) - DSTs (array/string slices) which work in VS & VS Code fail in CDB. - I've avoided `Mode::DebugInfoAll` as 3 debuggers leads to pow(2,3)=8 possible combinations. REFERENCE CDB is not part of the base Visual Studio install, but can be added via the Windows 10 SDK: https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk Installing just "Debugging Tools for Windows" is sufficient. CDB appears to already be installed on appveyor CI, where this changelist can find it, based on it's use here: https://github.com/rust-lang/rust/blob/0ffc57311030a1930edfa721fe57d0000a063af4/appveyor.yml#L227 CDB commands and command line reference: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-reference
2019-05-17Auto merge of #60171 - matthewjasper:full-nll-compare-mode, r=pnkfelixbors-2/+1
Use -Zborrowck=mir for NLL compare mode closes #56993 r? @pnkfelix
2019-05-17Rollup merge of #60805 - euclio:filetime-dep, r=Mark-SimulacrumMazdak Farrokhzad-14/+17
remove compiletest's dependency on `filetime`
2019-05-13remove compiletest's dependency on `filetime`Andy Russell-14/+17
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-27 09:07:36 +0000