From: "Leonardo Brás" <leobras.c@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>, paulmck@kernel.org
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH v1 2/2] utilities/gitlab-ci.yml: Add 'make check' on test_codesamples
Date: Mon, 06 Feb 2023 17:42:37 -0300 [thread overview]
Message-ID: <adef59f80e66063fef977449a71b880657e34701.camel@gmail.com> (raw)
In-Reply-To: <f051e079-4b6b-ff27-986d-ccd279ddd952@gmail.com>
On Sat, 2023-02-04 at 16:00 +0900, Akira Yokosawa wrote:
> On Sat, 04 Feb 2023 03:09:08 -0300, Leonardo Brás wrote:
> ...
> >
> > Thank you Paul!
> >
> > It looks like my pipeline failed with:
> >
> > sched_setaffinity: Invalid argument
> >
> > Which got me to look for some info:
> > - The Gitlab-CI instances are all single-cpu.
> >
> > Which got me thinking:
> > - How would we be able to test code for Parallel Programming in a single cpu?
>
> I assume you are using a runner gitlab provides.
> If this is the case, according to the page at gitlab:
>
> https://docs.gitlab.com/ee/ci/runners/saas/linux_saas_runner.html
>
> , there are three machine types you can choose.
>
> - Small: 1 vCPU (default)
> - Medium: 2 vCPUs
> - Large: 4 vCPUs (not available for free subscription)
>
> Hope this helps.
>
> Thanks, Akira
Sure it helps. Thanks Akira!
I will send a patch fixing this as soon as I test it first.
Best regards,
Leo
>
> >
> > Well, I still haven't debugged all this, after I am sure this is the issue, I
> > will reach people from Gitlab and check if is there any solution for this.
> >
> > Best regards,
> > Leo
>
prev parent reply other threads:[~2023-02-06 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 3:36 [PATCH v1 1/2] CodeSamples: Add check target to CodeSamples/ and count/ Makefiles Leonardo Bras
2023-02-04 3:36 ` [PATCH v1 2/2] utilities/gitlab-ci.yml: Add 'make check' on test_codesamples Leonardo Bras
2023-02-04 4:51 ` Paul E. McKenney
2023-02-04 6:09 ` Leonardo Brás
2023-02-04 7:00 ` Akira Yokosawa
2023-02-06 20:42 ` Leonardo Brás [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=adef59f80e66063fef977449a71b880657e34701.camel@gmail.com \
--to=leobras.c@gmail.com \
--cc=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.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).