From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: util-linux: update to 2.36.
Date: Tue, 28 Jul 2020 19:14:05 +0200 [thread overview]
Message-ID: <20200728171405.BnQpHqRa69JzUuKZhrsIOIfSRdwp_lpsY4VnNZiWjOg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23760@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
New comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/pull/23760#issuecomment-665165500
Comment:
> If it wouldn't lead to timeouts for most stuff, we should definitely run tests in travis. Still, we need to be able to run tests for essential software like this, at least locally, without having to figure out which tests are allowed to fail and whatnot.
Sure, but this is more of an upstream development issue, rather than an issue at this packaging level. If those failures are a real concern (for example the getopt posix ordering doesn't seem worrysome), then they should be addressed upstream and properly fixed either by addressing the real root cause, or by marking them as known-fails under musl.
next prev parent reply other threads:[~2020-07-28 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 10:39 [PR PATCH] " ailiop-git
2020-07-23 13:41 ` [PR REVIEW] " sgn
2020-07-23 13:53 ` [PR PATCH] [Updated] " ailiop-git
2020-07-28 7:56 ` sgn
2020-07-28 9:16 ` ailiop-git
2020-07-28 10:01 ` sgn
2020-07-28 12:21 ` ailiop-git
2020-07-28 14:32 ` sgn
2020-07-28 16:22 ` ailiop-git
2020-07-28 17:00 ` ericonr
2020-07-28 17:14 ` ailiop-git [this message]
2020-07-29 14:50 ` [PR PATCH] [Closed]: " sgn
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=20200728171405.BnQpHqRa69JzUuKZhrsIOIfSRdwp_lpsY4VnNZiWjOg@z \
--to=ailiop-git@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).