-
Notifications
You must be signed in to change notification settings - Fork 171
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
CI: fix timezone and pip3 issues #294
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Please wait until we agree on the way forward for open-amp and then we/I can update this one also. |
@arnopo are you going to do this one or do you want me to? I had it started but I don't have the change to use venv |
Both are ok for me. I'm waiting that we fix open-amp. I did not start libmetal update yet. |
* Lock to 24.04 so we control when to change * Update locale and timezone to work for 24.04 or 22.04 * 24.04 creates these files if not already there but 22.04 does not * Keep existing work around for 22.04 but make it work if already there * use venv * Breate a virtual environment isolated from the packages in the base environment * Inspired from zephyr build environment * Use pip3 everywhere removing global and --user installation Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
Force the exit with value 1 when cmake or make command fails. Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
The https://cfhcable.dl.sourceforge.net/project/freertos/FreeRTOS/V10.0.1/FreeRTOSv10.0.1.zip URL is no more valid Update it to point to sourceforge.net Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
I updated to use ubuntu 24.04 environement |
I pulled this down and pushed to my main branch to test on github. |
The zephyr failure appears to be a temp failure of the github web server. I ran the same thing again and it worked OK for zephyr. |
The Linux failures are hard to figure out. Initially they failed on the desktop, now they pass without me changing anything. They still fail on github but this does not cause a problem right now as github workflow ignores the error. I can't spend any more time on this right now so I suggest accepting this PR as is and we can fixup the Linux failures later (or delete them as they are redundant with the other test action). FYI: I tested this commit to fix github ignoring the test results. It does allow the workflow to fail but I don't have a fix or explanation of the failure right now. |
Yes I suspect that the issue is there since a while. As the workflow don't test the output it ignore the issue.
i will try to have a look this week. Ok to treat this in a separate PR/issue
|
The build check fails with following errors:
ln: failed to create symbolic link '/etc/localtime': File exists
Fix it by removing the link creation
error: externally-managed-environment
Fix it by adding "--break-system-packages" option to pip3