From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] Remaining issue with Dracut runtime tests
Date: Fri, 11 Nov 2022 21:53:21 +0100 [thread overview]
Message-ID: <20221111215321.7cfdbc46@windsurf> (raw)
Hello Yann,
Even after your recent Dracut runtime tests fixes there is still one issue:
======================================================================
FAIL: test_run (tests.fs.test_cpio.TestCpioDracutUclibcMergedUsr)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/builds/buildroot.org/buildroot/support/testing/tests/fs/test_cpio.py", line 105, in test_run
self.check_dracut()
File "/builds/buildroot.org/buildroot/support/testing/tests/fs/test_cpio.py", line 60, in check_dracut
self.assertNotEqual(out.find("usr/lib/libz.so"), -1)
AssertionError: -1 == -1
----------------------------------------------------------------------
See:
https://gitlab.com/buildroot.org/buildroot/-/jobs/3282261241
https://gitlab.com/buildroot.org/buildroot/-/jobs/3282261239
https://gitlab.com/buildroot.org/buildroot/-/jobs/3282261236
Could you have a look?
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-11-11 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 20:53 Thomas Petazzoni via buildroot [this message]
2022-11-12 9:07 ` [Buildroot] Remaining issue with Dracut runtime tests Yann E. MORIN
2022-11-12 10:15 ` Yann E. MORIN
2022-11-12 13:38 ` Yann E. MORIN
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=20221111215321.7cfdbc46@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.