debian-forge/osbuild/testutil
Tomáš Hozza 3ae8f25f55 Testutil/importlib: don't write bytecode when importing modules
Cache files will split the extension, this means that all pyc cache
files looks like we get many clashing `org.osbuild.cpython-py311.pyc
files. Moreover, the cache bytecode invalidation is based on the
timestamp (which is the same after git checkout) and the file size
(which may be the same for two different files). This means that we
can't rely on the cache files.

This issue has been found after the previous commit made the
`org.osbuild.systemd` and `org.osbuild.selinux` stages to have exactly
the same size, which caused the interpreter to reuse the bytecode for
the selinux stage when running unit tests for the systemd stage. This
resulted in consistent and weird failures when the systemd stage
options were passed to the selinux stage code.

The credit for this fix goes to Michael Vogt, who found the cause and
fix. Also thanks to Simon de Vlieger for his help with debugging the
problem.

Co-authored-by: Michael Vogt <michael.vogt@gmail.com>
Signed-off-by: Tomáš Hozza <thozza@redhat.com>
2024-04-22 16:33:59 +02:00
..
__init__.py testutil: extract find_one_subclass_in_module() helper 2024-04-03 11:36:01 +02:00
atomic.py testutil: add AtomicCounter() as a threadsafe counter 2024-04-09 03:02:45 +02:00
imports.py Testutil/importlib: don't write bytecode when importing modules 2024-04-22 16:33:59 +02:00
net.py testutil: skip tests for missing ThreadingHTTPServer in py36 2024-04-16 15:16:49 +02:00