From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rust: update to 1.52.1.
Date: Fri, 04 Jun 2021 08:36:20 +0200 [thread overview]
Message-ID: <20210604063620.dInh7MV4xLXvepYW6iVfdLGr1fGBgaD1bmniTzij1PE@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: 1124 bytes --]
New comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/30259#issuecomment-854402591
Comment:
This may be a lot simpler than I thought. I took a look in the `src/test/` directory, and if there was a "compile-fail" set of tests they don't exist anymore. The "run-fail" and it's sub-test listed in the template don't exist anymore either. Taking out the non-existent tests results in the check process proceeding as it should. I didn't have the forethought to redirect the output to a file and the amount of output exceeded my scrollback buffer, but from what I saw only a few tests failed out of the thousands that were run. I can try to get the full output and link it to here if that would be helpful.
If you want to take a look at the descriptions of all of the categories of available tests, check here: https://rustc-dev-guide.rust-lang.org/tests/intro.html. I don't know if any of them replace the ones that had to be taken out or if any of them even need replacing; that stuff is way over my head.
As a side note, is q66 still working on the ppc stuff for llvm12?
next prev parent reply other threads:[~2021-06-04 6:36 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
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 [this message]
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=20210604063620.dInh7MV4xLXvepYW6iVfdLGr1fGBgaD1bmniTzij1PE@z \
--to=cinerea0@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).