Your message dated Sat, 20 Sep 2025 17:28:08 +0100
with message-id <[email protected]>
and subject line rust-proc-macro2-diagnostics: autopkgtest failure
has caused the Debian Bug report #1102552,
regarding rust-proc-macro2-diagnostics: autopkgtest failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1102552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102552
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rust-proc-macro2-diagnostics
Version: 0.10.1-1
Severity: serious
https://tracker.debian.org/pkg/rust-proc-macro2-diagnostics
Issues preventing migration:
∙ ∙ autopkgtest for rust-proc-macro2-diagnostics/0.10.1-1: amd64: Regression or
new test ♻, arm64: Regression or new test ♻, armel: Regression or new test ♻,
armhf: Regression or new test ♻, i386: Regression or new test ♻, ppc64el:
Regression or new test ♻, riscv64: Regression or new test ♻, s390x: Regression
or new test ♻
...
64s EXPECTED:
64s ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
64s error: just an item error
64s = note: see an item
64s --> tests/stable/errors.rs:5:16
64s |
64s 5 | error: just an item error,
64s | ^^^^
64s
64s error: [help] I can help with that
64s --> tests/stable/errors.rs:7:15
64s |
64s 7 | help: I can help with that,
64s | ^
64s
64s error: just an expression error item context
64s = note: see an exp
64s = warning: kind of weird
64s --> tests/stable/errors.rs:11:16
64s |
64s 11 | error: just an expression error item context,
64s | ^^^^
64s
64s error: [help] I can help with that
64s --> tests/stable/errors.rs:14:15
64s |
64s 14 | help: I can help with that,
64s | ^
64s
64s error: just an expression error expr content
64s = warning: oh no
64s --> tests/stable/errors.rs:18:16
64s |
64s 18 | error: just an expression error expr content,
64s | ^^^^
64s
64s error: this is an item error message
64s --> tests/stable/errors.rs:24:12
64s |
64s 24 | error: this is an item error message,
64s | ^^^^
64s
64s error: this is an error message
64s = note: but it has a note
64s --> tests/stable/errors.rs:28:12
64s |
64s 28 | error: this is an error message,
64s | ^^^^
64s
64s error: hello
64s --> tests/stable/errors.rs:33:12
64s |
64s 33 | error: hello,
64s | ^^^^^
64s
64s error: [warning] just wanted to warn you
64s --> tests/stable/errors.rs:34:14
64s |
64s 34 | warning: just wanted to warn you,
64s | ^^^^
64s
64s error: [note] just jotting things down
64s = help: please help on that note
64s = note: notes on notes
64s --> tests/stable/errors.rs:35:11
64s |
64s 35 | note: just jotting things down,
64s | ^^^^
64s
64s error: [warning] hello not found
64s = note: just a note to say hi
64s = help: its a good idea to say hello
64s --> tests/stable/errors.rs:41:14
64s |
64s 41 | warning: hello not found,
64s | ^^^^^
64s
64s error: unknown diagnostic kind
64s = help: expected one of: 'error', 'warning', 'note', 'help'
64s = note: or their _ versions
64s --> tests/stable/errors.rs:47:5
64s |
64s 47 | hello: hello,
64s | ^^^^^
64s
64s error: [help] this is standalone help
64s = note: but we add things to it
64s = help: like more help
64s --> tests/stable/errors.rs:51:11
64s |
64s 51 | help: this is standalone help,
64s | ^^^^
64s ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
64s
64s ACTUAL OUTPUT:
64s ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
64s error[E0432]: unresolved import `diagnostic_example`
64s --> tests/stable/errors.rs:1:5
64s |
64s 1 | use diagnostic_example::{diagnostic_item, diagnostic_expr};
64s | ^^^^^^^^^^^^^^^^^^ use of undeclared crate or module
`diagnostic_example`
64s ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈
64s note: If the actual output is the correct output you can bless it by
rerunning
64s your test with the environment variable TRYBUILD=overwrite
64s
64s
64s
64s test main ... FAILED
64s
64s failures:
64s
64s ---- main stdout ----
64s
64s thread 'main' panicked at
/usr/share/cargo/registry/trybuild-1.0.99/src/run.rs:101:13:
64s 1 of 1 tests failed
64s stack backtrace:
64s 0: rust_begin_unwind
64s at /usr/src/rustc-1.85.0/library/std/src/panicking.rs:692:5
64s 1: core::panicking::panic_fmt
64s at /usr/src/rustc-1.85.0/library/core/src/panicking.rs:75:14
64s 2: trybuild::run::<impl trybuild::Runner>::run
64s at /usr/share/cargo/registry/trybuild-1.0.99/src/run.rs:101:13
64s 3: <trybuild::TestCases as core::ops::drop::Drop>::drop
64s at /usr/share/cargo/registry/trybuild-1.0.99/src/lib.rs:319:13
64s 4: core::ptr::drop_in_place<trybuild::TestCases>
64s at /usr/src/rustc-1.85.0/library/core/src/ptr/mod.rs:523:1
64s 5: main::main
64s at ./tests/main.rs:10:1
64s 6: main::main::{{closure}}
64s at ./tests/main.rs:2:10
64s 7: core::ops::function::FnOnce::call_once
64s at
/usr/src/rustc-1.85.0/library/core/src/ops/function.rs:250:5
64s 8: core::ops::function::FnOnce::call_once
64s at
/usr/src/rustc-1.85.0/library/core/src/ops/function.rs:250:5
64s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a
verbose backtrace.
64s
64s
64s failures:
64s main
64s
64s test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered
out; finished in 4.30s
...
--- End Message ---
--- Begin Message ---
Autopkgtests for 1.10.1-2 pass.
--- End Message ---
