From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Cc: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] submitted bugreport to upstream nmigen
Date: Fri, 3 Apr 2020 13:27:39 -0700
Message-ID: <6D952307-5237-462B-B209-E0DFDDDDF5A2@getmailspring.com> (raw)
In-Reply-To: <CAPweEDyB2Rng3Mm10ymgyz0WwY7EKHGLVgb4FT_1Xm7gOWZNRg@mail.gmail.com>
On Apr 3 2020, at 12:24 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Fri, Apr 3, 2020 at 7:26 PM Jacob Lifshay
> <programmerjake@gmail.com> wrote:
>
>> We can build it on any other gitlab installation, if all else fails,
>> we can
>> install gitlab on jacob-build-server.
>
> which has ridiculous resources (32 GB RAM for a start). plus, we have
> root access so can do backups etc.
>
> would you be happy for frieder to install gitlab on it? (the more
> people doing stuff in parallel the better).
>
> l.
I did a little bit of research on how gitlab archives build logs and
build artifacts.
https://docs.gitlab.com/ee/administration/job_artifacts.html
https://docs.gitlab.com/ee/administration/job_logs.html#new-incremental-logging-architecture
I believe this is their official tool for doing such things.
https://gitlab.com/gitlab-org/gitlab-workhorse
If you'd like I'd be willing to install gitlab and gitlab test runner on
my 2600x 32 GB machine, and purchase a sizable hard drive to serve as
one of the archives.
Is there some way that I can allocate only 2, 4, or 6 logical cores, and
say 12 or 16GB or ram, and 50MB/s of bandwidth? Perhaps I am not yet up
to the task of running a server on which the project critically depends.
But I do have these resources available, so if there is a way you can
think of making this useful and what you require please let me know.
Cole
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
prev parent reply index
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 3:21 Jacob Lifshay
2020-04-01 10:16 ` Luke Kenneth Casson Leighton
2020-04-02 3:03 ` Jacob Lifshay
2020-04-02 9:27 ` Luke Kenneth Casson Leighton
2020-04-02 18:19 ` Immanuel, Yehowshua U
2020-04-03 4:10 ` Jacob Lifshay
2020-04-03 10:37 ` Luke Kenneth Casson Leighton
2020-04-03 17:41 ` Jacob Lifshay
2020-04-03 18:11 ` Luke Kenneth Casson Leighton
2020-04-03 18:26 ` Jacob Lifshay
2020-04-03 19:24 ` Luke Kenneth Casson Leighton
2020-04-03 20:21 ` Jacob Lifshay
2020-04-03 21:48 ` Luke Kenneth Casson Leighton
2020-04-04 8:15 ` Frieder Paape
2020-04-04 11:07 ` Luke Kenneth Casson Leighton
2020-04-03 20:27 ` Cole Poirier [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=6D952307-5237-462B-B209-E0DFDDDDF5A2@getmailspring.com \
--to=colepoirier@gmail.com \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git