From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: uutils-0.0.24
Date: Mon, 05 Feb 2024 07:03:11 +0100 [thread overview]
Message-ID: <20240205060311.2F9C422BA2@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48534@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/48534#issuecomment-1926284059
Comment:
> In regards to x86_64-glibc, the package built fine
You need to do `./xbps-src pkg -Q uutils` or `./xbps-src check uutils` in order to run the tests.
Testing locally, the following tests do fail:
```
test_df::test_file_column_width_if_filename_contains_unicode_chars
test_df::test_nonexistent_file
test_df::test_output_file_specific_files
test_df::test_output_mp_repeat
test_df::test_output_option_without_equals_sign
test_df::test_total_label_in_correct_column
test_df::test_type_option_with_file
test_test::test_file_not_owned_by_egid
test_test::test_file_not_owned_by_euid
test_touch::test_touch_system_fails
```
The df test failures are related to `df` returning that no filesystems are mounted (which is expected for the chroot).
The other tests don't output any stderr but them not working correctly does seem expected for the chroot.
You could probably just patch out these tests.
> should I be checking x86_64-musl and i686-glibc locally (crossbuilds?)?
Those are not cross builds, they are native builds. (`-a i686` is cross and `-A i686` is native)
You can't run tests when cross compiling.
next prev parent reply other threads:[~2024-02-05 6:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 5:18 [PR PATCH] " caughtquick
2024-02-05 5:31 ` caughtquick
2024-02-05 5:38 ` oreo639
2024-02-05 5:39 ` oreo639
2024-02-05 5:40 ` oreo639
2024-02-05 5:42 ` oreo639
2024-02-05 5:50 ` caughtquick
2024-02-05 5:50 ` caughtquick
2024-02-05 5:59 ` oreo639
2024-02-05 6:00 ` oreo639
2024-02-05 6:00 ` oreo639
2024-02-05 6:03 ` oreo639 [this message]
2024-02-05 6:03 ` oreo639
2024-02-05 6:04 ` oreo639
2024-02-05 6:11 ` oreo639
2024-02-05 6:15 ` oreo639
2024-02-05 6:16 ` oreo639
2024-02-05 6:16 ` oreo639
2024-02-05 11:39 ` ahesford
2024-02-05 16:29 ` caughtquick
2024-05-06 1:46 ` github-actions
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=20240205060311.2F9C422BA2@inbox.vuxu.org \
--to=oreo639@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).