compliance-tool: Fix compliance tool imports and unitests #356
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The reason why the python 3.8 compliance-tool-test does not work seems to be because it seems to be generating older aas examples with spelling mistakes in the |
Frosty2500
force-pushed
the
fix_compliance_tool
branch
2 times, most recently
from
30c33be to
8881751
Compare
|
I just remembered that we do not support Python 3.8 anymore so that test not working does not matter. I will adapt the ci accordingly. |
s-heppner
requested changes
Jan 6, 2025
s-heppner
approved these changes
Jan 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently there are quite some wrong imports in the compliance-tool directory. Even when those are fixed many Unitests still fail.
Here these imports are fixed.
Fixes #354