From: jhe2 <jhe2@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: clevis-20
Date: Wed, 24 Jul 2024 20:53:25 +0200 [thread overview]
Message-ID: <20240724185325.2C0432277A@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51359@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
New review comment by jhe2 on void-packages repository
https://github.com/void-linux/void-packages/pull/51359#discussion_r1690286123
Comment:
Interestingly, if I manually build `jose` and then manually run the tests via `meson test` in my build directory, all tests pass, including the `alg_comp` test. So what I did was:
```
cd masterdir/builddir/jose-14
mkdir testbuild
cd testbuild
meson setup .. --prefix=/usr
ninja
meson test
```
So it appears that something in the build environment that `xbps-src` configures, causes that test to fail.
next prev parent reply other threads:[~2024-07-24 18:53 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-21 15:26 [PR PATCH] " jhe2
2024-07-21 15:41 ` [PR PATCH] [Updated] " jhe2
2024-07-21 15:46 ` jhe2
2024-07-21 15:52 ` jhe2
2024-07-21 17:49 ` [PR REVIEW] " classabbyamp
2024-07-21 17:49 ` classabbyamp
2024-07-21 17:49 ` classabbyamp
2024-07-21 17:49 ` classabbyamp
2024-07-21 17:49 ` classabbyamp
2024-07-21 17:49 ` classabbyamp
2024-07-21 17:49 ` classabbyamp
2024-07-21 19:13 ` [PR PATCH] [Updated] " jhe2
2024-07-21 19:18 ` [PR REVIEW] " jhe2
2024-07-21 19:20 ` jhe2
2024-07-21 19:21 ` jhe2
2024-07-21 19:21 ` jhe2
2024-07-21 19:25 ` jhe2
2024-07-21 19:33 ` [PR PATCH] [Updated] " jhe2
2024-07-21 19:34 ` [PR REVIEW] " jhe2
2024-07-21 19:35 ` [PR PATCH] [Updated] " jhe2
2024-07-21 19:45 ` jhe2
2024-07-21 19:54 ` [PR REVIEW] " jhe2
2024-07-21 19:55 ` [PR PATCH] [Updated] " jhe2
2024-07-21 21:59 ` [PR REVIEW] " classabbyamp
2024-07-21 22:08 ` classabbyamp
2024-07-21 22:09 ` classabbyamp
2024-07-21 22:09 ` classabbyamp
2024-07-22 8:16 ` [PR PATCH] [Updated] " jhe2
2024-07-22 8:17 ` [PR REVIEW] " jhe2
2024-07-22 8:17 ` jhe2
2024-07-22 9:01 ` jhe2
2024-07-24 18:45 ` jhe2
2024-07-24 18:53 ` jhe2 [this message]
2024-07-24 18:54 ` classabbyamp
2024-07-24 19:32 ` jhe2
2024-08-05 16:46 ` [PR PATCH] [Updated] " jhe2
2024-08-05 16:49 ` [PR REVIEW] " jhe2
2024-08-05 16:50 ` jhe2
2024-08-05 16:55 ` jhe2
2024-08-05 16:58 ` [PR PATCH] [Updated] " jhe2
2024-08-05 17:10 ` [PR REVIEW] " jhe2
2024-08-07 5:56 ` classabbyamp
2024-08-07 5:59 ` classabbyamp
2024-08-07 6:38 ` jhe2
2024-08-07 6:41 ` [PR PATCH] [Updated] " jhe2
2024-08-13 15:29 ` elivance
2024-08-13 17:04 ` jhe2
2024-08-14 2:40 ` elivance
2024-08-14 5:07 ` jhe2
2024-08-14 5:54 ` jhe2
2024-08-14 5:56 ` [PR PATCH] [Updated] " jhe2
2024-09-21 22:27 ` classabbyamp
2024-09-22 5:32 ` [PR PATCH] [Updated] " jhe2
2024-09-22 6:26 ` classabbyamp
2024-09-22 6:27 ` classabbyamp
2024-09-22 6:27 ` classabbyamp
2024-09-22 6:28 ` classabbyamp
2024-09-22 6:32 ` [PR PATCH] [Merged]: " classabbyamp
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=20240724185325.2C0432277A@inbox.vuxu.org \
--to=jhe2@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).