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 1/3] support/testing/tests/package/test_python_boto3: use ext2 instead of cpio
Date: Mon, 15 Aug 2022 23:48:13 +0200 [thread overview]
Message-ID: <20220815214815.2234201-2-thomas.petazzoni@bootlin.com> (raw)
In-Reply-To: <20220815214815.2234201-1-thomas.petazzoni@bootlin.com>
The CPIO filesystem generated by the test_python_boto3 test is too
large, and doesn't fit as an initramfs in the 256MB of RAM available
in the versatilepb machine. This causes a "Initramfs unpacking failed:
write error" when booting, and many files being missing from the root
filesystem, ultimately causing the test to fail.
It would make sense to switch all test cases to use ext2 + a
hard-drive, but for now, let's fix the few test cases that are causing
problems.
Fixes:
https://gitlab.com/buildroot.org/buildroot/-/jobs/2884635041
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
support/testing/tests/package/test_python_boto3.py | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/support/testing/tests/package/test_python_boto3.py b/support/testing/tests/package/test_python_boto3.py
index 756495fec9..7f24399304 100644
--- a/support/testing/tests/package/test_python_boto3.py
+++ b/support/testing/tests/package/test_python_boto3.py
@@ -1,4 +1,5 @@
from tests.package.test_python import TestPythonPackageBase
+import os
class TestPythonPy3Boto3(TestPythonPackageBase):
@@ -7,6 +8,17 @@ class TestPythonPy3Boto3(TestPythonPackageBase):
"""
BR2_PACKAGE_PYTHON3=y
BR2_PACKAGE_PYTHON_BOTO3=y
+ BR2_TARGET_ROOTFS_EXT2=y
+ BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
+ # BR2_TARGET_ROOTFS_TAR is not set
"""
sample_scripts = ["tests/package/sample_python_boto3.py"]
timeout = 10
+
+ def login(self):
+ ext2_file = os.path.join(self.builddir, "images", "rootfs.ext2")
+ self.emulator.boot(arch="armv5",
+ kernel="builtin",
+ options=["-drive", "file=%s,if=scsi,format=raw" % ext2_file],
+ kernel_cmdline=["rootwait", "root=/dev/sda"])
+ self.emulator.login()
--
2.37.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent 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 [Buildroot] [PATCH 0/3] Fix 3 Python test cases Thomas Petazzoni via buildroot
2022-08-15 21:48 ` Thomas Petazzoni via buildroot [this message]
2022-08-16 16:26 ` [Buildroot] [PATCH 1/3] support/testing/tests/package/test_python_boto3: use ext2 instead of cpio 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-2-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.