From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: vaultwarden: update to 1.27.0; vaultwarden-web: update to 2022.12.0.
Date: Sat, 31 Dec 2022 20:30:56 +0100 [thread overview]
Message-ID: <20221231193056.eH9MlaXmjdzCeDzPgpm7iqseKFO4-Ly3_HrCeQzS5n8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41049@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/41049#issuecomment-1368269458
Comment:
This is failing to build on i686 on the builders:
```
thread '<unnamed>' panicked at '/builddir/rustc-1.64.0-src/compiler/rustc_codegen_ssa/src/back/write.rs:1534:21: worker thread panicked', compiler/rustc_middle/src/util/bug.rs:36:26
stack backtrace:
0: 0xf45b25fa - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hacbd04ec4532a04b
1: 0xf46111a0 - core::fmt::write::h7228ce9ca3af089d
2: 0xf45a123c - <unknown>
3: 0xf45b4fdb - <unknown>
4: 0xf45b4cd8 - std::panicking::default_hook::h71921bb196a32bc0
5: 0xf4574c6c - <unknown>
6: 0xf4b9e723 - <unknown>
7: 0xf45b584f - std::panicking::rust_panic_with_hook::ha10eda39b41de8dc
8: 0xf6adb37d - <unknown>
9: 0xf6ad04de - <unknown>
10: 0xf4af5304 - <unknown>
11: 0xf6ac368a - <unknown>
12: 0xf6c2e428 - <unknown>
13: 0xf6bfe996 - <unknown>
14: 0xf6bfe8ea - <unknown>
15: 0xf6c2e377 - <unknown>
16: 0xf4afbf01 - <unknown>
17: 0xf4cdd279 - <unknown>
18: 0xf4cb84f4 - <unknown>
19: 0xf4ce2061 - <unknown>
20: 0xf45bfddb - <unknown>
fatal runtime error: Rust cannot catch foreign exceptions
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', cargo-auditable/src/rustc_wrapper.rs:91:39
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: could not compile `vaultwarden`
=> ERROR: vaultwarden-1.27.0_1: do_build: '${make_cmd} build --release --target ${RUST_TARGET} ${configure_args}' exited with 101
=> ERROR: in do_build() at common/build-style/cargo.sh:8
```
prev parent reply other threads:[~2022-12-31 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 1:24 [PR PATCH] vaultwarden-web: update to 2022.11.2 TinfoilSubmarine
2022-12-19 3:34 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-12-30 17:57 ` [PR PATCH] [Updated] vaultwarden-web: update to 2022.12.0 TinfoilSubmarine
2022-12-31 17:37 ` [PR PATCH] [Merged]: vaultwarden: update to 1.27.0; " paper42
2022-12-31 19:30 ` paper42 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221231193056.eH9MlaXmjdzCeDzPgpm7iqseKFO4-Ly3_HrCeQzS5n8@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).