Skip to content

Resolve issue with GitHub Actions runner running out of disk space #93

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

Merged
merged 7 commits into from
Aug 6, 2024

Conversation

willtai
Copy link
Contributor

@willtai willtai commented Aug 5, 2024

Description

  • For E2E tests, prune docker images before installing dependencies to reduce disk file usage
  • Adds a new workflow for running E2E tests on main every 3 hours
  • Reduces scope (Python versions and Neo4j community Docker image) of PR E2E tests

Type of Change

  • New feature
  • Bug fix
  • Breaking change
  • Documentation update
  • Project configuration change

Complexity

Complexity: Low

How Has This Been Tested?

  • Unit tests
  • E2E tests
  • Manual tests

Checklist

The following requirements should have been met (depending on the changes in the branch):

  • Documentation has been updated
  • Unit tests have been updated
  • E2E tests have been updated
  • Examples have been updated
  • New files have copyright header
  • CLA (https://neo4j.com/developer/cla/) has been signed
  • CHANGELOG.md updated if appropriate

@willtai willtai marked this pull request as ready for review August 5, 2024 09:22
@willtai willtai force-pushed the fix-out-of-space-error-on-gh-actions branch from 13c5cbc to a0acb2a Compare August 5, 2024 11:15
Comment on lines 4 to 7
push:
branches:
- main
- fix-out-of-space-error-on-gh-actions
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I will remove this after the review. This is to test that this workflow works when I push to my working branch

Co-authored-by: Oskar Hane <oh@oskarhane.com>
@willtai willtai requested a review from a team August 5, 2024 15:46

on:
schedule:
- cron: '0 6,9,12,15,18 * * 1-5' # Runs every 3 hours daytime on working days
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we really need a cron job? Can't we just run it every time there is a push to the main branch?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We could, but it won't run if there hasn't been a push to main in a long time, which is why I have both. Is there a concern with doing this every 3 hours?

Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry I'm confused, what are we testing if there is no change? The latest versions of the dependencies?

Copy link
Contributor

Choose a reason for hiding this comment

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

Why would we needed to run them again if there hasn't been a push to main in a while?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The latest versions of the dependencies

Yes especially external integrations such as Pinecone and Weaviate. Do you think this will be likely to change?

I don't see a downside to having this run periodically as the job will likely take about 10 minutes.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok, I see now, sounds good. Thanks!

Copy link
Contributor

Choose a reason for hiding this comment

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

Do we not fix the versions of those though?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

weaviate-client = "^4.6.1"

We fix the minimum version, it will install the latest version but not the next major version

@willtai willtai merged commit 337aeba into neo4j:main Aug 6, 2024
11 checks passed
a-s-g93 pushed a commit to a-s-g93/neo4j-genai-python-dev that referenced this pull request Sep 13, 2024
…eo4j#93)

* Reduce parallelism

* Docker pruning

* Max parallel 3 jobs

* Increase concurrent limit to 6

* New workflow for scheduled E2E tests on main

* Update .github/workflows/scheduled-e2e-tests.yaml

Co-authored-by: Oskar Hane <oh@oskarhane.com>

* Removed push rules from pr-e2e-tests.yaml

---------

Co-authored-by: Oskar Hane <oh@oskarhane.com>
@willtai willtai deleted the fix-out-of-space-error-on-gh-actions branch October 1, 2024 11:02
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.

4 participants