Repository navigation
regression: parameter may not live long enough #104445
Description
- https://crater-reports.s3.amazonaws.com/beta-1.66-1.2/beta-2022-11-01/gh/OliverEvans96.payments-engine-example/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.66-1.2/beta-2022-11-01/gh/broxus.nekoton-wasm/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.66-1.2/beta-2022-11-01/gh/lukechu10.maple-trunk-gitpod-template/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.66-1.2/beta-2022-11-01/gh/sycamore-rs.sycamore-rocket-template/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.66-1.2/beta-2022-11-01/gh/sycamore-rs.sycamore-rocket/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.66-1.2/beta-2022-11-01/gh/kyrosle.webcam-live/log.txt
Activity
- addedT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.Performance or correctness regression from stable to beta.
on Nov 15, 2022 - addedI-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}Issue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
on Nov 15, 2022 I've bisected the first and last crate in the list, both point to commit f5193a9 -> #95474 cc @oli-obk
bisected with cargo-bisect-rustc v0.6.0
Host triple: x86_64-unknown-linux-gnu
Reproduce with:cargo bisect-rustc 2022-03-01 --preserve
since they're regressions on existing crates, let's label them as
P-criticalout of caution to signal that we want them checked before the next stable@rustbot label -I-prioritize +P-critical
- addedP-criticalCritical priorityCritical priorityand removedI-prioritizeIssue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}Issue needs a team member to assess the impact. Will be replaced by P-{low,medium,high,critical}
on Nov 15, 2022 It doesn't look like they were noted in the PR run (unless I'm missing the relevant comment). I think given the volume of breakage it likely makes sense to move ahead, but it would be great to put up PRs to these crates.
- https://crater-reports.s3.amazonaws.com/beta-1.66-1.2/beta-2022-11-01/gh/OliverEvans96.payments-engine-example/log.txt
- https://crater-reports.s3.amazonaws.com/beta-1.66-1.2/beta-2022-11-01/gh/lukechu10.maple-trunk-gitpod-template/log.txt
- sycamore failure
- https://crater-reports.s3.amazonaws.com/beta-1.66-1.2/beta-2022-11-01/gh/sycamore-rs.sycamore-rocket-template/log.txt
- fix PR already landed
- https://crater-reports.s3.amazonaws.com/beta-1.66-1.2/beta-2022-11-01/gh/sycamore-rs.sycamore-rocket/log.txt
- sycamore failure
- https://crater-reports.s3.amazonaws.com/beta-1.66-1.2/beta-2022-11-01/gh/kyrosle.webcam-live/log.txt
- sycamore failure
This is known breakage, not release blocking, and is mentioned in release notes (https://github.com/rust-lang/rust/pull/104405/files#diff-4a00447b47c36ebd3ded77321deff288e424f4605496ee1199fc9953a20f4473R77). Resolving.