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

Travis build OOMs out if the automated tests have too many vertices #32

Open
idcrosby opened this issue Jan 3, 2019 · 5 comments
Open
Assignees

Comments

@idcrosby
Copy link
Contributor

idcrosby commented Jan 3, 2019

No description provided.

@idcrosby
Copy link
Contributor Author

idcrosby commented Jan 3, 2019

see https://travis-ci.com/SeMI-network/weaviate-infra/builds/95625854 for an example of the OOM error

@etiennedi
Copy link
Member

etiennedi commented Jan 3, 2019

Just to verify I understand the issue correctly:

  • Weaviate is running in k8s (deployed via helm setup)
  • The verification script is running on k8s as well (deployed via kubectl run)
  • All pods and their containers are fine, i.e. they are no OOM kills from kubernetes
  • The travis build itself is OOM killed while the verification script is running.

Correct?

@idcrosby
Copy link
Contributor Author

idcrosby commented Jan 3, 2019

@etiennedi yes that's correct

@etiennedi
Copy link
Member

Ah, just saw kubectl logs -f verification-ptt7m exited with 137

Maybe wee could wait for the script to finish and only get the logs once with --tail <reasonableNumber>. I guess the most interesting info is the benchmarks at the end?

@bobvanluijt
Copy link
Member

Curious to what the status is of this issue.

@idcrosby idcrosby self-assigned this Jan 29, 2019
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

No branches or pull requests

3 participants