-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.1.1: Failing tests due to missing files #66
Comments
This issue was resolved in #70 |
Now there are assertion errors
It also prints lots of these warnings
|
This is weird... What OS do you use? Because our internal tests on Win10, 11 Mac 13, and Ubuntu 22, 24 are passing just fine... |
Gentoo |
Here's the complete build.log |
I'm not completely sure what has happened there, but in the log I see that tests are failing only for unusual (almost bizarre) combinations of key and hash. For example: SECP256 has passed using SHA256 but failed for any other. RSA has passed with SHA256 but failed for any other. SECP384 passed only with SHA384... |
If it helps, these are the versions: Do you think it's not critical? I can mark them xfail? |
There are only few combinations that are mandatory. I'll split the test scope into "mandatory" and "optional" and mark the "optional" ones with |
I don't have access to a Gentoo machine, please try to run the test from branch 66-211-failing-tests-due-to-missing-files |
Tests are successful now, here's the summary:
There are also some warnings printed by setuptools but these aren't critical and the the package still installs with them. This isn't really related to the issue in question but I thought I'd mention it.
|
Yes, we know about the setuptools warnings. It's not a big deal. Those folders contain only data files, no source code. |
Hi! 👋
When trying to upgrade the package on Arch Linux to 2.1.1 I ran into quite a few failing tests due to missing files.
Build/check logs:
python-spsdk-2.1.1-1-x86_64-build.log
python-spsdk-2.1.1-1-x86_64-check.log
I'm already skipping some doc tests as they are not relevant for our use-case, but the above failures appear to be due to missing files.
When looking at e.g.
ls -lah /var/lib/archbuild/extra-testing-x86_64/dave-5/build/python-spsdk/src/spsdk-2.1.1/tests/nxpimage/data/workspace/cfgs/lpc55s3x/ total 128K drwxr-xr-x 1 dave dave 1.2K Mar 31 17:09 . drwxr-xr-x 1 dave dave 130 Mar 31 17:09 .. -rw-r--r-- 1 dave dave 2.1K Mar 31 17:09 mb_ext_xip_crc.yaml -rw-r--r-- 1 dave dave 1.6K Mar 31 17:09 mb_ext_xip_crc_s19.yaml -rw-r--r-- 1 dave dave 2.7K Mar 31 17:09 mb_ext_xip_signed.yaml -rw-r--r-- 1 dave dave 2.1K Mar 31 17:09 mb_ram_crc.yaml -rw-r--r-- 1 dave dave 2.2K Mar 31 17:09 mb_ram_crc_version.yaml -rw-r--r-- 1 dave dave 3.1K Mar 31 17:09 mb_xip_256_none.yaml -rw-r--r-- 1 dave dave 2.6K Mar 31 17:09 mb_xip_256_none_no_tz.yaml -rw-r--r-- 1 dave dave 2.6K Mar 31 17:09 mb_xip_384_256.yaml -rw-r--r-- 1 dave dave 2.9K Mar 31 17:09 mb_xip_384_256_cert.yaml -rw-r--r-- 1 dave dave 1.5K Mar 31 17:09 mb_xip_384_256_cert_invalid.json -rw-r--r-- 1 dave dave 2.6K Mar 31 17:09 mb_xip_384_384.yaml -rw-r--r-- 1 dave dave 3.0K Mar 31 17:09 mb_xip_384_384_cert.yaml -rw-r--r-- 1 dave dave 2.1K Mar 31 17:09 mb_xip_crc.yaml -rw-r--r-- 1 dave dave 3.8K Mar 31 17:09 sb3_256_256.yaml -rw-r--r-- 1 dave dave 4.4K Mar 31 17:09 sb3_256_256_cert.yaml -rw-r--r-- 1 dave dave 5.4K Mar 31 17:09 sb3_256_256_notime.yaml -rw-r--r-- 1 dave dave 3.9K Mar 31 17:09 sb3_256_none.yaml -rw-r--r-- 1 dave dave 3.6K Mar 31 17:09 sb3_256_none_ernad.yaml -rw-r--r-- 1 dave dave 3.8K Mar 31 17:09 sb3_384_256.yaml -rw-r--r-- 1 dave dave 4.2K Mar 31 17:09 sb3_384_256_cert.yaml -rw-r--r-- 1 dave dave 3.8K Mar 31 17:09 sb3_384_256_fixed_timestamp.yaml -rw-r--r-- 1 dave dave 4.1K Mar 31 17:09 sb3_384_256_unencrypted.yaml -rw-r--r-- 1 dave dave 3.5K Mar 31 17:09 sb3_384_384.yaml -rw-r--r-- 1 dave dave 3.9K Mar 31 17:09 sb3_384_384_cert.yaml -rw-r--r-- 1 dave dave 3.9K Mar 31 17:09 sb3_384_none.yaml -rw-r--r-- 1 dave dave 11K Mar 31 17:09 sb3_test_384_384_unencrypted.yaml
I will disable all tests in question.
The text was updated successfully, but these errors were encountered: