https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=beta 2025-07-19T16:44:07+00:00 2025-07-19T16:44:07+00:00 Martin Nordholts martin.nordholts@codetale.se 2025-06-25T05:56:40+00:00 urn:sha1:e1d4f2a0c297690ddfc24815de57539f532f2471 And introduce two new directives for ui tests: * `run-crash` * `run-fail-or-crash` Normally a `run-fail` ui test like tests that panic shall not be terminated by a signal like `SIGABRT`. So begin having that as a hard requirement. Some of our current tests do terminate by a signal/crash however. Introduce and use `run-crash` for those tests. Note that Windows crashes are not handled by signals but by certain high bits set on the process exit code. Example exit code for crash on Windows: `0xc000001d`. Because of this, we define "crash" on all platforms as "not exit with success and not exit with a regular failure code in the range 1..=127". Some tests behave differently on different targets: * Targets without unwind support will abort (crash) instead of exit with failure code 101 after panicking. As a special case, allow crashes for `run-fail` tests for such targets. * Different sanitizer implementations handle detected memory problems differently. Some abort (crash) the process while others exit with failure code 1. Introduce and use `run-fail-or-crash` for such tests. 2025-03-30T17:33:15+00:00 Urgau urgau@numericable.fr 2025-03-09T21:23:31+00:00 urn:sha1:aa8848040a160842d47a5a143e04da8ad9f27613 2024-10-09T23:34:27+00:00 Ben Kimock kimockb@gmail.com 2024-10-07T23:34:25+00:00 urn:sha1:84dacc18829e24ec5d61087a233de68ef57dfabc