public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Benda Xu <heroxbd@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-dev-announce] Gentoo CI news: pkgcheck is now running truly parallel
Date: Tue, 08 Oct 2019 15:57:38 +0800	[thread overview]
Message-ID: <87k19f3c0d.fsf@gentoo.org> (raw)
In-Reply-To: <e35e794e7483436e0154adb134c36b48eb83c63a.camel@gentoo.org> ("Michał Górny"'s message of "Mon, 07 Oct 2019 21:58:28 +0200")

[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]

Michał Górny <mgorny@gentoo.org> writes:

> Just a quick note: thanks to hard work of radhermit, the newest release
> of pkgcheck features internal parallelization of checks.  While it's not
> perfect and there's still room for improvement (I mean, it could run
> even faster!), it's a major step forward.
>
> This means that I've finally retired that ugly hack that split
> categories into multiple groups and ran them in parallel.  This means
> that CI is no longer bound by the longest category (hello, media-libs/)
> and can utilize all 32 cores instead of ~14.
>
> This also means that if you're planning to run tree-wide scans with
> pkgcheck, you no longer have to employ huge hacks to make them faster. 
> You just run it normally!  In your face, repoman!
>
> Once again, thanks to radhermit.  His work on pkgcheck is astonishing,
> and it's becoming a great tool for developers.

A big round of applause to radhermit for the better QA tool!

Thank you to all who contributed.

Benda

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2019-10-08  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07 19:58 [gentoo-dev] Gentoo CI news: pkgcheck is now running truly parallel Michał Górny
2019-10-08  7:57 ` Benda Xu [this message]

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=87k19f3c0d.fsf@gentoo.org \
    --to=heroxbd@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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