https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=try 2025-07-21T09:16:20+00:00 2025-07-21T09:16:20+00:00 Tshepang Mbambo hopsi@tuta.io 2025-07-21T09:16:20+00:00 urn:sha1:62e3a05291ef782cf212675d9e13c0b937c788c8 Rustc pull update 2025-07-21T08:53:11+00:00 Tshepang Mbambo hopsi@tuta.io 2025-07-21T08:53:11+00:00 urn:sha1:79e3c7df0b63dcce4c17c7133564882672c6de34 2025-07-21T04:17:50+00:00 The rustc-josh-sync Cronjob Bot github-actions@github.com 2025-07-21T04:17:50+00:00 urn:sha1:ad20b064c30bbe9626e8c99f2b455cc6fd836d18 Pull recent changes from https://github.com/rust-lang/rust via Josh. Upstream ref: 460259d14de0274b97b8801e08cb2fe5f16fdac5 Filtered ref: 599ee17eb87c83f97eb37fd9fe264da65d4c9461 This merge was created using https://github.com/rust-lang/josh-sync. 2025-07-21T04:17:44+00:00 The rustc-josh-sync Cronjob Bot github-actions@github.com 2025-07-21T04:17:44+00:00 urn:sha1:897d007f8f2d4018fba5f2884cb1b45846d8a371 This updates the rust-version file to 460259d14de0274b97b8801e08cb2fe5f16fdac5. 2025-07-20T12:44:01+00:00 Guillaume Gomez guillaume1.gomez@gmail.com 2025-07-18T10:05:08+00:00 urn:sha1:4a35a9f074f5df8ce0d1f14d8569da3b6badfc01 2025-07-20T12:43:59+00:00 Guillaume Gomez guillaume1.gomez@gmail.com 2025-07-18T09:52:54+00:00 urn:sha1:9944139f70f2423f572ce48675458ccb67bb8d46 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-07-18T11:06:50+00:00 Yiqun Liu ffengyu964@gmail.com 2025-07-18T11:06:50+00:00 urn:sha1:eda2d0d2365d913022e9626acf9767fbf17f62e6 2025-07-18T02:27:54+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-07-18T02:27:54+00:00 urn:sha1:37e7bc1296aee2f6362cf26dda95fd4f8afe4ff7 rustc-dev-guide subtree update r? ghost 2025-07-17T10:06:26+00:00 Deadbeef ent3rm4n@gmail.com 2025-07-13T08:49:19+00:00 urn:sha1:69326878eeabb713e2d4a85215b87f18e498313c