-
Notifications
You must be signed in to change notification settings - Fork 164
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
Specifying PYTHONPATH for contrib builds #361
Conversation
Background: If not set the local vspec will not be first candidate, as it is not located under contrib. Instead a cached version might be used, which might not be compatible with the current vss-tools version
@danielwilms - I believe this solves the issue we have seen recently on failing contrib-builds in CI. More info on background: We noticed that many contrib builds failed (even those expected to pass). Daniel noticed that a cached vss-tools vspec module seemed to be used. I noticed that it seemed to be an error sometimes appearing, sometimes not. This is likely related to the recent introduction of With my limited knowledge it seems Python prefer a cached vspec module rather than something located in |
More details on the problem, showing two recent builds. https://github.com/COVESA/vehicle_signal_specification/runs/4176114945?check_suite_focus=true This build works as expected, there are problems building vspec2c and vspec2ocf due to that those tools have not been updated for a while, but the errors are as expected.
https://github.com/COVESA/vehicle_signal_specification/runs/4163571834?check_suite_focus=true In this build the problem is visible. It complains on that
|
Great that it fixes the build for now. Wondering if we should extend pythonpath instead of overwriting. Then we should consider to implement COVESA/vss-tools#114, which should solve this one as well I'd say. |
You mean something like below?
|
@oliveirarleo please have a look, if it's referenced correctly in python scripts |
Turns out that putting |
The PR at vss-tools #119 solves this issue. |
Seems to be correct, I will close this PR. Thanks for the help and analysis @oliveirarleo |
Background:
If not set the local vspec will not be first candidate,
as it is not located under contrib.
Instead a cached version might be used, which might not be compatible
with the current vss-tools version