-
Notifications
You must be signed in to change notification settings - Fork 508
Gh actions debug #2883
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
Gh actions debug #2883
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.
Pull Request Overview
This PR fixes the working directory issue in the Python regression test GitHub action by switching from runner.workspace to github.workspace, and updates caching to use artifacts instead of the actions/cache mechanism.
- Updated working directory references throughout the workflow
- Replaced caching with artifact upload/download to share build outputs between jobs
Add space for clarity Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
andrew-platt
left a comment
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.
Looks good and tests ok.
This PR is ready to be merged.
Feature or improvement description
This PR fixes the issue with Python not being able to find the
requirements.txtfile in the regression test GitHub action. The issue was caused by not specifying or using the wrong variable for the working directory when runningpip install -r requirements.txt. Different runners would interpret the working directory differently causing tests to sometimes pass and sometimes fail. This PR uses${{github.workspace}}instead of${{runner.workspace}}to specify the working directory.In addition, the existing regression test GitHub action uses caches to transfer data and binaries between the jobs in a run. Based on https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/storing-and-sharing-data-from-a-workflow#comparing-artifacts-and-dependency-caching, artifacts should be used for sharing data within a run (across jobs) and caches should be used for sharing dependencies across workflow runs. This PR changes the action to use artifacts, which reduces storage size and makes it possible for the user to download the compilation output after the run, which may be useful.
Related issue, if one exists
Impacted areas of the software
automated-dev-tests.yml