From: "Lance Albertson via RT" <hosting-request@osuosl.org>
To: mark@klomp.org
Cc: buildbot@sourceware.org
Subject: [support.osuosl.org #32563] Request CI hosting for builder.sourceware.org
Date: Fri, 5 Aug 2022 14:52:14 -0700 [thread overview]
Message-ID: <rt-4.0.4-183567-1659736334-553.32563-6-0@osuosl.org> (raw)
In-Reply-To: <rt-4.0.4-171867-1659734276-616.32563-6-0@osuosl.org>
On Fri Aug 05 14:17:56 2022, mark@klomp.org wrote:
> On Fri, Aug 05, 2022 at 08:52:58AM -0700, Lance Albertson via RT wrote:
> > Is there anything else you need for this?
>
> No, looks great. I'll play with it this weekend to enable some larger
> testsuites using all 16 CPUs.
Excellent. Going ahead and closing this ticket then.
--
Lance Albertson
Director
Oregon State University | Open Source Lab
prev parent reply other threads:[~2022-08-05 21:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-32563@osuosl.org>
[not found] ` <Yp5+pqvhR8WYiaqq@wildebeest.org>
[not found] ` <rt-4.0.4-32453-1654617175-469.32563-6-0@osuosl.org>
2022-06-07 22:24 ` Mark Wielaard
[not found] ` <rt-4.0.4-80639-1654640709-839.32563-6-0@osuosl.org>
2022-06-16 17:40 ` Lance Albertson via RT
2022-06-16 22:49 ` Mark Wielaard
2022-06-16 22:49 ` via RT
[not found] ` <rt-4.0.4-176523-1655419769-1468.32563-6-0@osuosl.org>
2022-06-20 19:36 ` Lance Albertson via RT
2022-06-20 22:06 ` Mark Wielaard
2022-06-20 22:06 ` via RT
[not found] ` <rt-4.0.4-135343-1655762795-1742.32563-6-0@osuosl.org>
2022-08-05 0:29 ` Lance Albertson via RT
2022-08-05 1:30 ` Mark Wielaard
2022-08-05 1:31 ` via RT
[not found] ` <rt-4.0.4-195587-1659663068-623.32563-6-0@osuosl.org>
2022-08-05 15:52 ` Lance Albertson via RT
2022-08-05 21:17 ` Mark Wielaard
2022-08-05 21:17 ` via RT
[not found] ` <rt-4.0.4-171867-1659734276-616.32563-6-0@osuosl.org>
2022-08-05 21:52 ` Lance Albertson via RT [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=rt-4.0.4-183567-1659736334-553.32563-6-0@osuosl.org \
--to=hosting-request@osuosl.org \
--cc=buildbot@sourceware.org \
--cc=mark@klomp.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 read-only IMAP folder(s) and NNTP newsgroup(s).