From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rust: update to 1.52.1.
Date: Sun, 23 May 2021 15:26:34 +0200 [thread overview]
Message-ID: <20210523132634.Q-AjCrTduMGra9BXiBLiEFEt7RUyhgpJ9l1tD1HoYUg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30259@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2372 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/30259#issuecomment-846563195
Comment:
Tests fail for me
```
=> rust-1.52.1_1: running do_check ...
Finished dev [unoptimized + debuginfo] target(s) in 0.24s
warning: x.py has made several changes recently you may want to look at
help: consider looking at the changes in `src/bootstrap/CHANGELOG.md`
note: to silence this warning, add `changelog-seen = 2` at the top of `config.toml`
thread 'main' panicked at 'error: no rules matched src/test/compile-fail', src/bootstrap/builder.rs:225:17
stack backtrace:
0: rust_begin_unwind
at /rustc/88f19c6dab716c6281af7602e30f413e809c5974/library/std/src/panicking.rs:493:5
1: std::panicking::begin_panic_fmt
at /rustc/88f19c6dab716c6281af7602e30f413e809c5974/library/std/src/panicking.rs:435:5
2: bootstrap::builder::StepDescription::run
at ./src/bootstrap/builder.rs:225:17
3: bootstrap::builder::Builder::run_step_descriptions
at ./src/bootstrap/builder.rs:571:9
4: bootstrap::builder::Builder::execute_cli
at ./src/bootstrap/builder.rs:563:9
5: bootstrap::Build::build
at ./src/bootstrap/lib.rs:506:17
6: bootstrap::main
at ./src/bootstrap/bin/main.rs:33:5
7: core::ops::function::FnOnce::call_once
at /rustc/88f19c6dab716c6281af7602e30f413e809c5974/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
failed to run: /builddir/rustc-1.52.1-src/build/bootstrap/debug/bootstrap test -j8 --no-doc --no-fail-fast src/test/codegen src/test/codegen-units src/test/compile-fail src/test/incremental src/test/mir-opt src/test/pretty src/test/run-fail src/test/run-fail/pretty src/test/run-make src/test/run-make-fulldeps src/test/ui src/test/ui-fulldeps
Build completed unsuccessfully in 0:00:00
=> ERROR: rust-1.52.1_1: do_check: 'python3 x.py test ${makejobs} --no-doc --no-fail-fast src/test/codegen src/test/codegen-units src/test/compile-fail src/test/incremental src/test/mir-opt src/test/pretty src/test/run-fail src/test/run-fail/pretty src/test/run-make src/test/run-make-fulldeps src/test/ui src/test/ui-fulldeps' exited with 1
=> ERROR: in do_check() at srcpkgs/rust/template:304
```
next prev parent reply other threads:[~2021-05-23 13:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 6:36 [PR PATCH] [wip] rust: update to 1.51.0 ericonr
2021-04-16 6:56 ` [PR PATCH] [Updated] " ericonr
2021-04-16 13:02 ` ericonr
2021-04-16 23:21 ` ericonr
2021-04-16 23:34 ` ericonr
2021-04-17 5:20 ` ericonr
2021-04-17 23:51 ` ericonr
2021-04-18 0:03 ` ericonr
2021-05-06 17:47 ` cinerea0
2021-05-06 18:31 ` ericonr
2021-05-10 22:44 ` cinerea0
2021-05-10 22:57 ` ericonr
2021-05-12 14:20 ` [PR PATCH] [Updated] " ericonr
2021-05-12 14:22 ` rust: update to 1.52.1 ericonr
2021-05-12 20:12 ` ericonr
2021-05-12 20:13 ` [PR PATCH] [Updated] " ericonr
2021-05-22 4:47 ` rustysec
2021-05-22 6:05 ` ericonr
2021-05-23 13:26 ` paper42 [this message]
2021-05-25 14:53 ` ericonr
2021-05-27 10:35 ` paper42
2021-06-03 16:18 ` cinerea0
2021-06-03 20:14 ` paper42
2021-06-04 4:53 ` cinerea0
2021-06-04 6:35 ` cinerea0
2021-06-04 6:36 ` cinerea0
2021-06-07 4:29 ` cinerea0
2021-06-07 4:31 ` cinerea0
2021-06-07 4:37 ` cinerea0
2021-06-17 20:15 ` [PR PATCH] [Updated] " ericonr
2021-06-17 20:17 ` [PR PATCH] [Updated] rust: update to 1.53.0 ericonr
2021-06-17 23:15 ` ericonr
2021-06-26 22:08 ` [PR PATCH] [Updated] " ericonr
2021-07-01 17:32 ` cinerea0
2021-07-04 20:42 ` ericonr
2021-07-04 20:42 ` [PR PATCH] [Closed]: " ericonr
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=20210523132634.Q-AjCrTduMGra9BXiBLiEFEt7RUyhgpJ9l1tD1HoYUg@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).