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

fix: check the activation script exists on Python virtual environments #29265

Merged
merged 3 commits into from
Dec 6, 2021

Conversation

kuisathaverat
Copy link
Contributor

@kuisathaverat kuisathaverat commented Dec 3, 2021

What does this PR do?

It changes the way to check if the Python virtual environment is valid, not it check for the activation script instead of check only the existence of the folder.

Why is it important?

For some reason, the folder exists in the CI and it is empty, this forces to recreate it in case the activation script is not there.

Checklist

  • My code follows the style guidelines of this project
  • [ ] I have commented my code, particularly in hard-to-understand areas
  • [ ] I have made corresponding changes to the documentation
  • [ ] I have made corresponding change to the default configuration files
  • [ ] I have added tests that prove my fix is effective or that my feature works
  • [ ] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Dec 3, 2021
@elasticmachine
Copy link
Collaborator

elasticmachine commented Dec 3, 2021

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-12-03T16:03:15.766+0000

  • Duration: 14 min 5 sec

  • Commit: 61dce1c

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@kuisathaverat kuisathaverat self-assigned this Dec 3, 2021
@kuisathaverat kuisathaverat added bug ci Team:Automation Label for the Observability productivity team labels Dec 3, 2021
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Dec 3, 2021
@kuisathaverat kuisathaverat requested review from a team December 3, 2021 16:05
@kuisathaverat kuisathaverat marked this pull request as ready for review December 3, 2021 16:06
@kuisathaverat kuisathaverat changed the title test: Test python fix: check the activation script exists on Python virtual environments Dec 3, 2021
@kuisathaverat kuisathaverat added backport-v8.0.0 Automated backport with mergify backport labels Dec 3, 2021
@ruflin ruflin merged commit 52e87f0 into elastic:7.16 Dec 6, 2021
@ruflin
Copy link
Collaborator

ruflin commented Dec 6, 2021

I directly got this merged to update the related PR's.

@kuisathaverat This should also be forwardported to master I assume?

mergify bot pushed a commit that referenced this pull request Dec 6, 2021
ruflin pushed a commit that referenced this pull request Dec 6, 2021
#29265) (#29279)

(cherry picked from commit 52e87f0)

Co-authored-by: Ivan Fernandez Calvo <[email protected]>
@v1v v1v added the backport-v8.1.0 Automated backport with mergify label Dec 6, 2021
mergify bot pushed a commit that referenced this pull request Dec 6, 2021
ruflin pushed a commit that referenced this pull request Dec 13, 2021
#29265) (#29288)

(cherry picked from commit 52e87f0)

Co-authored-by: Ivan Fernandez Calvo <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport backport-v8.0.0 Automated backport with mergify backport-v8.1.0 Automated backport with mergify bug ci Team:Automation Label for the Observability productivity team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants