Register new CI lab for LoongArch testing

[Lincoln Lavoie]

Thanks Gaojuxin,

Cheers,
Lincoln

On Wed, May 6, 2026 at 3:30 AM 高巨鑫 <gaojuxin at loongson.cn> wrote:

>  Hi Lincoln,
>
>  Thanks for following up on this.
>
>  I've investigated and resolved the issues with the loongson CI lab. The
> main problems were:
>
>
>
>  1. DNS resolution failure - The loongson machine couldn't resolve
> external domains (patches.dpdk.org), which prevented the CI from fetching
> test tasks. This has been fixed.
>
>  2. GitHub connectivity - Connection to github.com was intermittent. I've
> configured git to use a proxy permanently.
>
>  After the fixes, I've re-run all the previously failed series (37863,
> 37871, 37874, 37875, 37884, 37902, 37904, 37912, 37913, 37914, 37921) and
> submitted the test results.
>
>
>  Regarding the "unknown failures" reported - these are expected on
> LoongArch architecture. 36 test cases fail due to architecture-specific
> limitations (such as eal_flags_*, mbuf_autotest, timer_autotest, etc.),
> which are not actual CI
>  issues but rather unsupported features on LoongArch.
>
>  The CI lab is now operational and running normally.
>
>
>
>
>  Cheers,
>
>
>
>  Gaojuxin
>
>
> -----原始邮件-----
> 发件人: "Lincoln Lavoie" <lylavoie at iol.unh.edu>
> 发送时间: 2026-05-01 03:40:01 (星期五)
> 收件人: 高巨鑫 <gaojuxin at loongson.cn>
> 抄送: ci at dpdk.org
> 主题: Re: Register new CI lab for LoongArch testing
>
> Hello Gaojuxin,
>
> Follow up on this to check on the status of the loongson unit testing, as
> there still seem to be a lot of failures being reported, including
> timeouts, etc.  Are you able to check on the status of the CI lab?
>
> Cheers,
> Lincoln
>
> On Thu, Apr 9, 2026 at 2:37 AM Thomas Monjalon <thomas at monjalon.net>
> wrote:
> OK
>
> Please check loongson-unit-loongarch64 which is failing on many patches.
> You should probably disable it while fixing it.
>
>
> 09/04/2026 04:26, 高巨鑫:
> > Hi Thomas,
> >
> > Thank you for the clarification.
> >
> > We will rename our labels as suggested to include the ABI version:
> >
> > - ABI 1.0 lab (Loongnix-Server 8.3, kernel 4.19, GCC 8.3):
> >     loongson-compile-loongarch-abi1
> >     loongson-unit-loongarch-abi1
> >
> > - ABI 2.0 lab (Loongnix-Server 23.2, kernel 6.6.52, GCC 12.3):
> >     loongson-compile-loongarch-abi2
> >     loongson-unit-loongarch-abi2
> >
> > Best regards,
> > Gaojuxin
> > Loongson Technology
> >
> >
> > > -----原始邮件-----
> > > 发件人: "Thomas Monjalon" <thomas at monjalon.net>
> > > 发送时间:2026-04-08 00:05:50 (星期三)
> > > 收件人: 高巨鑫 <gaojuxin at loongson.cn>
> > > 抄送: ci at dpdk.org
> > > 主题: Re: Register new CI lab for LoongArch testing
> > >
> > > 03/04/2026 03:44, 高巨鑫:
> > > > Hi all,
> > > >
> > > > Thank you for the feedback regarding the sender email address.
> > > >
> > > > We will use our existing system email address qemudev at loongson.cn
> > > > for the new CI lab as well. This address is already whitelisted.
> > > >
> > > > To clarify our CI lab setup:
> > > >
> > > > - ABI 1.0 lab (Loongnix-Server 8.3, kernel 4.19, GCC 8.3):
> > > >     labels: loongarch-compilation, loongarch-unit-testing
> > > >     sender: qemudev at loongson.cn (already whitelisted)
> > > >
> > > > - ABI 2.0 lab (Loongnix-Server 23.2, kernel 6.6.52, GCC 12.3):
> > > >     labels: loongson-compile-loongarch64, loongson-unit-loongarch64
> > > >     sender: qemudev at loongson.cn (same address, already whitelisted)
> > > >
> > > > Could you please register the two new labels for the ABI 2.0 lab:
> > > >   - loongson-compile-loongarch64
> > > >   - loongson-unit-loongarch64
> > >
> > > I don't think the labels have to be registered somewhere.
> > >
> > > May I suggest a rename of your labels, including ABI-1 and ABI-2 in
> the names?
> > >
> >
> >
> > ------------------------------
> > 系统研发部    高巨鑫
> >
> -----------------------------------------------------------------------------------------
> > 北京市海淀区中关村环保科技示范园龙芯产业园2号楼   100095
> > 电话: +86 (10) 62546668-4136
> > 手机: +86 15733091031
> > 邮箱: gaojuxin at loongson.cn
> > www.loongson.cn
> >
> >
> >
> >
> 本邮件及其附件含有龙芯中科的商业秘密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制或散发）本邮件及其附件中的信息。如果您错收本邮件，请您立即电话或邮件通知发件人并删除本邮件。
> > This email and its attachments contain confidential information from
> Loongson Technology , which is intended only for the person or entity whose
> address is listed above. Any use of the information contained herein in any
> way (including, but not limited to, total or partial disclosure,
> reproduction or dissemination) by persons other than the intended
> recipient(s) is prohibited. If you receive this email in error, please
> notify the sender by phone or email immediately and delete it.
> >
> >
> >
>
>
>
>
> --
> Lincoln Lavoie
> Principal Engineer, Broadband Technologies
> 21 Madbury Rd., Ste. 100, Durham, NH 03824
> lylavoie at iol.unh.edu
> https://www.iol.unh.edu
> +1-603-674-2755 (m)
>
>
> ------------------------------
> 系统研发部    高巨鑫
>
> -----------------------------------------------------------------------------------------
> 北京市海淀区中关村环保科技示范园龙芯产业园2号楼   100095
> 电话: +86 (10) 62546668-4136
> 手机: +86 15733091031
> 邮箱: gaojuxin at loongson.cn
> www.loongson.cn
>
>
>
> 本邮件及其附件含有龙芯中科的商业秘密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制或散发）本邮件及其附件中的信息。如果您错收本邮件，请您立即电话或邮件通知发件人并删除本邮件。
>
> This email and its attachments contain confidential information from
> Loongson Technology , which is intended only for the person or entity whose
> address is listed above. Any use of the information contained herein in any
> way (including, but not limited to, total or partial disclosure,
> reproduction or dissemination) by persons other than the intended
> recipient(s) is prohibited. If you receive this email in error, please
> notify the sender by phone or email immediately and delete it.
>
>
>

-- 
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie at iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mails.dpdk.org/archives/ci/attachments/20260506/d8a49779/attachment.htm>