unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Greg Hogan <code@greghogan.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 60020@debbugs.gnu.org
Subject: [bug#60020] [PATCH 0/8] Update openjdk.
Date: Tue, 17 Jan 2023 11:04:40 -0500	[thread overview]
Message-ID: <CA+3U0ZkqfK0FQ5JVDDWmn8OEyR9QJJdmbg=-rYzU6BRueCLzyg@mail.gmail.com> (raw)
In-Reply-To: <87a62i5pjc.fsf@gmail.com>

On Mon, Jan 16, 2023 at 12:59 PM Maxim Cournoyer
<maxim.cournoyer@gmail.com> wrote:
>
> Hello,
>
> Greg Hogan <code@greghogan.com> writes:
>
> > These look to be the latest updates to openjdk11+.
> >
> > The openjdk build process creates thousands of defunct bash processes,
> > necessitating the increase in maximum number of tasks.
> >
> > Greg Hogan (8):
> >   Increase "TasksMax" in 'guix-daemon.service'.
>
> This doesn't appear to have been merged yet.  Is it still needed?

Yes. Do we know what TasksMax is set to on the build farms?

> >   gnu: openjdk11: Update to 11.0.17.
> >   gnu: openjdk13: Update to 13.0.13.
> >   gnu: openjdk15: Update to 15.0.9.
> >   gnu: openjdk16: Update to 16.0.2.
> >   gnu: openjdk17: Update to 17.0.5.
> >   gnu: openjdk18: Update to 18.0.2.
> >   gnu: openjdk: Update to 19.
>
> These appear to have been merged already.  Feel free to close if there's
> nothing left to do here.

Everything except openjdk@19 was merged, so I don't know if that was
an editorial decision by the committer because version 19 was so new
(19.0.1 has since been released). I would close this ticket except for
waiting to confirm and accept the increase to TasksMax.

> --
> Thanks,
> Maxim




  reply	other threads:[~2023-01-17 16:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 21:18 [bug#60020] [PATCH 0/8] Update openjdk Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 1/8] Increase "TasksMax" in 'guix-daemon.service' Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 2/8] gnu: openjdk11: Update to 11.0.17 Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 3/8] gnu: openjdk13: Update to 13.0.13 Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 4/8] gnu: openjdk15: Update to 15.0.9 Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 5/8] gnu: openjdk16: Update to 16.0.2 Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 6/8] gnu: openjdk17: Update to 17.0.5 Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 7/8] gnu: openjdk18: Update to 18.0.2 Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 8/8] gnu: openjdk: Update to 19 Greg Hogan
2023-01-16 17:59 ` [bug#60020] [PATCH 0/8] Update openjdk Maxim Cournoyer
2023-01-17 16:04   ` Greg Hogan [this message]
2023-01-17 19:38     ` Maxim Cournoyer
2023-01-18  9:40       ` Efraim Flashner
2023-01-18 15:03         ` bug#60020: " Greg Hogan
2023-01-18 15:45           ` [bug#60020] " Maxim Cournoyer

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+3U0ZkqfK0FQ5JVDDWmn8OEyR9QJJdmbg=-rYzU6BRueCLzyg@mail.gmail.com' \
    --to=code@greghogan.com \
    --cc=60020@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).