From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: gaosong <gaosong@loongson.cn>, Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org
Cc: "Zhiguo Wu" <wuzhiguo@loongson.cn>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Bibo Mao" <maobibo@loongson.cn>,
"Xiaojuan Yang" <yangxiaojuan@loongson.cn>,
"Beraldo Leal" <bleal@redhat.com>, "WANG Xuerui" <git@xen0n.name>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Xianglai Li" <lixianglai@loongson.cn>,
"Tianrui Zhao" <zhaotianrui@loongson.cn>
Subject: Re: [PATCH 1/2] gitlab: Introduce Loongarch64 runner
Date: Thu, 11 Jan 2024 14:11:01 +0100 [thread overview]
Message-ID: <b10e1e42-f765-45d8-affc-784849a51854@linaro.org> (raw)
In-Reply-To: <93861775-6cc5-fb52-8926-9c85fe42b932@loongson.cn>
On 11/1/24 13:05, gaosong wrote:
> 在 2024/1/11 下午4:26, Thomas Huth 写道:
>> On 11/01/2024 08.25, gaosong wrote:
>>> Hi,
>>>
>>> 在 2024/1/11 下午3:08, Thomas Huth 写道:
>>>> On 02/01/2024 18.22, Philippe Mathieu-Daudé wrote:
>>>>> Full build config to run CI tests on a Loongarch64 host.
>>>>>
>>>>> Forks might enable this by setting LOONGARCH64_RUNNER_AVAILABLE
>>>>> in their CI namespace settings, see:
>>>>> https://www.qemu.org/docs/master/devel/ci.html#maintainer-controlled-job-variables
>>>>>
>>>>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>>>>> ---
>>>>> docs/devel/ci-jobs.rst.inc | 6 ++++++
>>>>> .gitlab-ci.d/custom-runners.yml | 1 +
>>>>> .../openeuler-22.03-loongarch64.yml | 21
>>>>> +++++++++++++++++++
>>>>> 3 files changed, 28 insertions(+)
>>>>> create mode 100644
>>>>> .gitlab-ci.d/custom-runners/openeuler-22.03-loongarch64.yml
>>>>>
>>>> ...
>>>>> diff --git a/.gitlab-ci.d/custom-runners.yml
>>>>> b/.gitlab-ci.d/custom-runners.yml
>>>>> index 8e5b9500f4..152ace4492 100644
>>>>> --- a/.gitlab-ci.d/custom-runners.yml
>>>>> +++ b/.gitlab-ci.d/custom-runners.yml
>>>>> @@ -32,3 +32,4 @@ include:
>>>>> - local: '/.gitlab-ci.d/custom-runners/ubuntu-22.04-aarch64.yml'
>>>>> - local: '/.gitlab-ci.d/custom-runners/ubuntu-22.04-aarch32.yml'
>>>>> - local: '/.gitlab-ci.d/custom-runners/centos-stream-8-x86_64.yml'
>>>>> + - local:
>>>>> '/.gitlab-ci.d/custom-runners/openeuler-22.03-loongarch64.yml'
>>>>> diff --git
>>>>> a/.gitlab-ci.d/custom-runners/openeuler-22.03-loongarch64.yml
>>>>> b/.gitlab-ci.d/custom-runners/openeuler-22.03-loongarch64.yml
>>>>> new file mode 100644
>>>>> index 0000000000..86d18f820e
>>>>> --- /dev/null
>>>>> +++ b/.gitlab-ci.d/custom-runners/openeuler-22.03-loongarch64.yml
>>>>> @@ -0,0 +1,21 @@
>>>>> +openeuler-22.03-loongarch64-all:
>>>>> + extends: .custom_runner_template :-)
>>>>> + needs: []
>>>>> + stage: build
>>>>> + tags:
>>>>> + - oe2203
>>>>> + - loongarch64
>>>>> + rules:
>>>>> + - if: '$CI_PROJECT_NAMESPACE == "qemu-project" &&
>>>>> $CI_COMMIT_BRANCH =~ /^staging/'
>>>>> + when: manual
>>>>> + allow_failure: true
>>>>> + - if: "$LOONGARCH64_RUNNER_AVAILABLE"
>>>>> + when: manual
>>>>> + allow_failure: true
>>>>> + script:
>>>>> + - mkdir build
>>>>> + - cd build
>>>>> + - ../configure
>>>>> + || { cat config.log meson-logs/meson-log.txt; exit 1; }
>>>>> + - make --output-sync -j`nproc --ignore=40`
>>>>> + - make --output-sync -j`nproc --ignore=40` check
>>>>
>>>> Does this system really have more than 40 CPU threads? Or is this a
>>>> copy-n-past from one of the other scripts? In the latter case, I'd
>>>> suggest to adjust the --ignore=40 to a more reasonable value.
>>>>
>>>> Thomas
>>> No, only 32. I think it should be --ignore=32 or 16.
>>
>> --ignore=32 then also does not make much sense, that would still be
>> the same as simply omitting the -j parameter. I guess --ignore=16
>> should be fine.
>>
>>> I create a same runner on this machine, and I find some check error.
>>> but I am not sure how to fix it. :-)
>>>
>>> See:
>>>
>>> https://gitlab.com/gaosong/qemu/-/jobs/5906269934
>>
>> Seems to be related to RAM backing... for example, the erst-test is
>> failing, which is doing something like:
>>
>> setup_vm_cmd(&state,
>> "-object memory-backend-file,"
>> "mem-path=acpi-erst.XXXXXX,"
>> "size=64K,"
>> "share=on,"
>> "id=nvram "
>> "-device acpi-erst,"
>> "memdev=nvram");
>>
>> So it seems like -object memory-backend-file" is not correctly working
>> in your gitlab runner? Is there some setup missing?
>>
>> Thomas
>>
>>
> This is my runner config.
>
> concurrent = 32
> check_interval = 0
> shutdown_timeout = 0
>
> [session_server]
> session_timeout = 1800
>
> ...
>
> [[runners]]
> name = "loongarch64"
> request_concurrency = 24
> url = "https://gitlab.com"
> id = 31426483
> token = "glrt-bGugocYrR2yqcu3ma7ka"
> token_obtained_at = 2024-01-10T08:31:29Z
> token_expires_at = 0001-01-01T00:00:00Z
> executor = "shell"
> builds_dir = "/data/gitlab-runner/builds"
> cache_dir = "/data/gitlab-runner/cache"
> [runners.cache]
> MaxUploadedArchiveSize = 0
>
> I create a project runner 'loongarch64' for my branch ci-master.
> Do we need some special configuration?
We need to follow this process:
https://lore.kernel.org/qemu-devel/20240104160805.56856-1-philmd@linaro.org/
next prev parent reply other threads:[~2024-01-11 13:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 17:22 [PATCH 0/2] gitlab: Add config for Loongarch64 custom runner Philippe Mathieu-Daudé
2024-01-02 17:22 ` [PATCH 1/2] gitlab: Introduce Loongarch64 runner Philippe Mathieu-Daudé
2024-01-11 7:08 ` Thomas Huth
2024-01-11 7:25 ` gaosong
2024-01-11 8:26 ` Thomas Huth
2024-01-11 12:05 ` gaosong
2024-01-11 13:11 ` Philippe Mathieu-Daudé [this message]
2024-01-12 9:52 ` gaosong
2024-01-15 10:08 ` gaosong
2024-01-02 17:22 ` [NOTFORMERGE PATCH 2/2] gitlab: Add Loongarch64 KVM-only build Philippe Mathieu-Daudé
2024-01-11 7:10 ` Thomas Huth
2024-01-11 7:37 ` gaosong
2024-01-11 8:20 ` Thomas Huth
2024-01-11 8:50 ` gaosong
2024-01-11 9:04 ` Thomas Huth
2024-01-11 9:51 ` gaosong
2024-01-11 11:26 ` Philippe Mathieu-Daudé
2024-01-11 11:41 ` gaosong
2024-01-24 8:56 ` gaosong
2024-01-11 9:26 ` Philippe Mathieu-Daudé
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=b10e1e42-f765-45d8-affc-784849a51854@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=gaosong@loongson.cn \
--cc=git@xen0n.name \
--cc=lixianglai@loongson.cn \
--cc=maobibo@loongson.cn \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=wuzhiguo@loongson.cn \
--cc=yangxiaojuan@loongson.cn \
--cc=zhaotianrui@loongson.cn \
/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 NNTP newsgroup(s).