From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: cargo-crev: update to 0.20.1
Date: Mon, 04 Oct 2021 22:34:11 +0200 [thread overview]
Message-ID: <20211004203411.DpmEtOLP9437XoDlY-YMktwBNmZcRG9jGcv5VnDR9_8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33251@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
New comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/33251#issuecomment-933834455
Comment:
Running the tests locally results in the same error found in CI here:
```
running 1 test
test creates_new_id_implicitly ... FAILED
failures:
---- creates_new_id_implicitly stdout ----
thread 'creates_new_id_implicitly' panicked at 'assertion failed: c.run(&[\"id\", \"trust\", \"--level=medium\",\n \"FYlr8YoYGVvDwHQxqEIs89reKKDy-oWisoO0qXXEfHE\"], \"\").status.success()', cargo-crev/tests/clitest.rs:11:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
failures:
creates_new_id_implicitly
test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.05s
```
What's interesting is the tests you linked show version 0.21.1 of cargo-crev being compiled, but that version doesn't seem to exist yet.
next prev parent reply other threads:[~2021-10-04 20:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 3:39 [PR PATCH] " cinerea0
2021-10-02 19:43 ` ericonr
2021-10-04 1:05 ` cinerea0
2021-10-04 2:12 ` ericonr
2021-10-04 20:34 ` cinerea0 [this message]
2021-10-29 3:47 ` cinerea0
2021-10-30 18:51 ` ericonr
2021-10-30 20:27 ` [PR PATCH] [Updated] " cinerea0
2021-10-30 23:58 ` cargo-crev: update to 0.21.1 cinerea0
2021-10-31 1:05 ` [PR PATCH] [Merged]: " 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=20211004203411.DpmEtOLP9437XoDlY-YMktwBNmZcRG9jGcv5VnDR9_8@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).