Skip to content
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

Use venv in CI #379

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Use venv in CI #379

wants to merge 2 commits into from

Conversation

Hardcode84
Copy link
Contributor

No description provided.

Signed-off-by: Ivan Butygin <[email protected]>
Signed-off-by: Ivan Butygin <[email protected]>
@Hardcode84 Hardcode84 changed the title venv Use venv in CI Jan 10, 2025
@Hardcode84 Hardcode84 marked this pull request as ready for review January 10, 2025 17:40
@Hardcode84 Hardcode84 requested a review from ScottTodd January 10, 2025 17:40
Comment on lines +49 to +50
source ${VENV_DIR}/bin/activate
echo PATH=$PATH >> $GITHUB_ENV
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not keep the venv active across job steps from what I can tell.

See that the logs are not using .turbine-venv: https://github.com/iree-org/iree-turbine/actions/runs/12714371230/job/35446471647?pr=379#step:5:20

I usually explicitly activate the venv in each step that needs it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the jobs in this file run on ephemeral github-hosted machines, using a virtual environment is less important. Could keep the file as-is, with pip caching.

Not that much of a difference in time though:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants