Repository navigation
add relnotes 1.99.0 - #163435
add relnotes 1.99.0#163435
Conversation
|
If it's not already the case, make sure to also merge the changes in the |
|
@rustbot ping relnotes-interest-group |
|
Hi relnotes-interest-group, this issue/PR could use some help in reviewing / cc @alex-semenyuk @jieyouxu @joshtriplett @lcnr @traviscross @weihanglo |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
[stable] 1.99.0 release https://forge.rust-lang.org/release/process.html#stable-pr Cherry-picks current state of relnotes (#163435), ultimately the main branch will have the authoritative copy unless we rebuild artifacts for some reason. r? me
|
@bors squash msg="add relnotes 1.99.0" |
This comment has been minimized.
This comment has been minimized.
Co-authored-by: Asger Hautop Drewsen <asger@tyilo.com> Co-authored-by: Boxy <rust@boxyuwu.dev> Co-authored-by: Mark Rousskov <mark.simulacrum@gmail.com> Co-authored-by: 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com>
|
🔨 6 commits were squashed into da3a408. |
8bced44 to
da3a408
Compare
|
@bors r+ p=1 rollup |
add relnotes 1.99.0 r? mark-simulacrum cc @rust-lang/release
add relnotes 1.99.0 r? mark-simulacrum cc @rust-lang/release
add relnotes 1.99.0 r? mark-simulacrum cc @rust-lang/release
|
@bors p=9 This needs to land by tomorrow morning (US Eastern) to be ready by the release, so bumping priority a bit more. I'm expecting it'll get pulled into rollups sufficient to make that happen (as per the above). |
|
The queue is not very large atm, let's reduce risk and just run this on its own after the PR that is currently running :) |
This comment has been minimized.
This comment has been minimized.
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 1625626 (parent) -> 21b707e (this PR) Test differencesShow 2 test diffs2 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 21b707e3f97e0b522ebd2f277a862339625ad83f --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (21b707e): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 2.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 0.4%, secondary 14.5%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 489.563s -> 487.961s (-0.33%) |
View all comments
r? mark-simulacrum
cc @rust-lang/release