From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Buildroot List" <buildroot@buildroot.org>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
"Romain Naour" <romain.naour@gmail.com>,
"Raphaël Mélotte" <raphael.melotte@mind.be>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH 0/3] Fix 3 Python test cases
Date: Mon, 15 Aug 2022 23:48:12 +0200 [thread overview]
Message-ID: <20220815214815.2234201-1-thomas.petazzoni@bootlin.com> (raw)
Hello,
This small patch series fixes 3 Python test cases. They fail because
we use an initramfs in all Python tests (and in many other tests). The
issue of initramfs is that if the initramfs filesystem grows too
large, the kernel fails to decompress it, and simply continues booting
with a partially uncompressed initramfs: some files are simply
missing.
In this patch series, we fix just the 3 failing test cases, for the
sake of having a reasonably minimal solution to apply in master. We
switch those test cases to use an initramfs to using an ext2 image
that is exposed by Qemu as a regular hard-drive.
Long term, we probably want to switch all tests to using this
strategy, so that we don't face a weird limit caused by
initramfs. That being said, there is no silver bullet: even if we
switch to ext2, we will have to define, for each test, the size of the
ext2 filesystem image. So there will still be some sort of arbitrary
limit that will have to be tweaked from time to time as a given test
grows in size (more dependencies, dependencies growing, etc.).
Best regards,
Thomas Petazzoni
Thomas Petazzoni (3):
support/testing/tests/package/test_python_boto3: use ext2 instead of
cpio
support/testing/tests/package/test_python_botocore: use ext2 instead
of cpio
support/testing/tests/package/test_python_s3transfer: use ext2 instead
of cpio
support/testing/tests/package/test_python_boto3.py | 12 ++++++++++++
.../testing/tests/package/test_python_botocore.py | 12 ++++++++++++
.../testing/tests/package/test_python_s3transfer.py | 12 ++++++++++++
3 files changed, 36 insertions(+)
--
2.37.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-08-15 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 21:48 Thomas Petazzoni via buildroot [this message]
2022-08-15 21:48 ` [Buildroot] [PATCH 1/3] support/testing/tests/package/test_python_boto3: use ext2 instead of cpio Thomas Petazzoni via buildroot
2022-08-16 16:26 ` Yann E. MORIN
2022-08-16 20:42 ` Thomas Petazzoni via buildroot
2022-08-15 21:48 ` [Buildroot] [PATCH 2/3] support/testing/tests/package/test_python_botocore: " Thomas Petazzoni via buildroot
2022-08-15 21:48 ` [Buildroot] [PATCH 3/3] support/testing/tests/package/test_python_s3transfer: " Thomas Petazzoni via buildroot
2022-08-16 20:59 ` [Buildroot] [PATCH 0/3] Fix 3 Python test cases 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=20220815214815.2234201-1-thomas.petazzoni@bootlin.com \
--to=buildroot@buildroot.org \
--cc=raphael.melotte@mind.be \
--cc=romain.naour@gmail.com \
--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.