[do not merge] crater dbg! changes against stable-1.95.0

[dianne]

stable backport of #155915 for crater

[dianne]

@bors try

[rust-bors]

💔 Test for 1190584 failed: CI. Failed job:

• try - dist-x86_64-linux (web logs, enhanced plaintext logs)

[dianne]

do I need to make an imaginary version bump? I guess I can try that

I guess I could also maybe have made this PR against the beta branch and just ignored the known regressions in the crater results? I'm not sure what the usual process is for cratering isolated changes against stable

[dianne]

sorry if that pinged anyone! maybe I need to make a fake point release? though just in case, @bors try

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

  CACHE_DOMAIN: ci-caches.rust-lang.org
  PR_CI_JOB: 1
  IMAGE: pr-check-1
##[endgroup]
error: PRs changing the `beta` channel should be sent to the `beta` branch!
##[error]Process completed with exit code 1.
##[group]Run echo "disk usage:"
echo "disk usage:"
df -h
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}

[rust-bors]

☀️ Try build successful (CI)
Build commit: eed2451 (eed2451ff9b5f723c5709802779b044cd4dfff59, parent: 59807616e1fa2540724bfbac14d7976d7e4a3860)

[dianne]

closing in favor of crater run directly on #155915