Description: After exporting the tests and running the test suite parselogs the test fails because in dmesg_output.log the line "ACPI: _OSC evaluation for CPUs failed, trying _PDC" is considered a failure. Normally this line should be ignored in the test and is listed in the file "oe-core/meta/lib/oeqa/runtime/cases/parselogs-ignores-common.txt" Steps to reproduce: - configure build: in local.conf add IMAGE_CLASSES += "testexport" TEST_TARGET_IP = "IP-address-for-the-test-target" TEST_SERVER_IP = "IP-address-for-the-test-server" - build image - export tests: bitbake image -c testexport - run image: e.g with QEMU - execute tests: e.g cd tmp/testimage/image ./oe-test runtime #runs all tests Actual result: parselogs test fails because of "harmless" log entry Expected Result: pareslogs test should pass Build Date & Hardware: Build 2025-09-05 on Dockercontainer running Debian 12 Reason: The "oe-core/meta/classes-recipe/testexport.bbclass" is not packing the parselogs-ignores-*.txt files into the tarball. Suggestion: Always pack all parselogs-ignores-*.txt files. E.g: in testexport.bbclass line 121 add: import glob parselogs_ignores = glob.glob(os.path.join(corebase_path, 'meta', 'lib', 'oeqa', 'runtime', 'cases', 'parselogs-ignores-*.txt')) for f in parselogs_ignores: shutil.copy2(f, cases_path)
Looks good, can you send your patch? YP Bug review.
Hallo Randy, Yes I hope I can do that during this week. I still have some company internal issues setting up our SMTP server for sending the patch, but I hope that will be solved soon :) This is the first time I will hand in a bug, do I need to change the status to IN PROGRESS IMPLEMENTATION?
Thanks Barne! There are few firm rules for the YP bugzilla status but I've set the status as you mentioned mostly to take it out of Needinfo, because Stephen does track that status to ensure that things don't stall. Good luck with the setup and please let me know if you need some help.
> Hello, > Took me a while but I was able to build master now and yes, the > parselogs_ignores_*.txt files are in the testexport.tar.gz Sorry for > not checking that before, I only looked into the reported bugs. Lesson > learned. I guess the patch can then be rejected 😊
closing bug since not an issue on master branch any more