From: Logarithmus <Logarithmus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] common/build-style/: enable running tests in parallel
Date: Wed, 14 Jul 2021 17:09:13 +0200 [thread overview]
Message-ID: <20210714150913.-xabWdjoEpsaPe5KSPGmtU2SaPNuiyO6y2xEMFWjNwE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31811@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
New comment by Logarithmus on void-packages repository
https://github.com/void-linux/void-packages/pull/31811#issuecomment-879974474
Comment:
> Should we add `disable_parallel_tests` to override this? Some test suites are explicitly broken when run in parallel (iirc cups, for example).
>
> I assume they left their approval so others could review.
I've added `disable_parallel_check` option and tested it for `mold`, it works as intended.
A little TODO:
- document the new option in `Manual.md`
- try running tests for `cups*` packages and see if it fail without `disable_parallel_check`.
next prev parent reply other threads:[~2021-07-14 15:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 1:29 [PR PATCH] " Logarithmus
2021-07-05 23:37 ` [RFC] " Logarithmus
2021-07-05 23:46 ` ericonr
2021-07-06 1:51 ` q66
2021-07-14 14:51 ` [PR PATCH] [Updated] " Logarithmus
2021-07-14 15:09 ` Logarithmus [this message]
2021-07-14 15:09 ` Chocimier
2021-07-14 15:09 ` Logarithmus
2021-07-14 15:10 ` [PR PATCH] [Updated] " Logarithmus
2021-07-14 15:12 ` Logarithmus
2021-07-14 15:24 ` Chocimier
2021-07-14 15:24 ` [PR REVIEW] " sgn
2021-07-14 15:29 ` sgn
2021-07-24 12:01 ` Logarithmus
2021-07-24 12:04 ` Logarithmus
2021-07-24 12:16 ` sgn
2021-07-24 12:30 ` [PR PATCH] [Updated] " Logarithmus
2021-07-24 12:31 ` Logarithmus
2021-07-25 19:53 ` [PR REVIEW] " Logarithmus
2021-07-25 19:54 ` Logarithmus
2021-07-30 20:43 ` Chocimier
2022-05-24 2:13 ` github-actions
2022-06-08 2:11 ` [PR PATCH] [Closed]: " 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=20210714150913.-xabWdjoEpsaPe5KSPGmtU2SaPNuiyO6y2xEMFWjNwE@z \
--to=logarithmus@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).