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

Testing fails due to job killed by travis #99

Open
holgerteichgraeber opened this issue Jul 3, 2019 · 5 comments
Open

Testing fails due to job killed by travis #99

holgerteichgraeber opened this issue Jul 3, 2019 · 5 comments
Assignees

Comments

@holgerteichgraeber
Copy link
Owner

Testing sometimes fails. The error is something like /home/travis/.travis/functions: line 104: 3596 Killed. This seems to be an issue with memory on travis.

Todo is to rewrite the tests so that they use less memory. Potentially make the kmedoids-exact cbc case smaller, and also reduce the amount of data that is loaded.

Workaround for now is to just rerun the build on travis, so far it has worked the second time.

@holgerteichgraeber
Copy link
Owner Author

See for example this discussion: travis-ci/travis-ci#4192

@holgerteichgraeber
Copy link
Owner Author

@YoungFaithful
Copy link
Collaborator

Does the "reference" data ( test/reference_generation/run_clust.jld2 ) already contain the new Object names based on TimSeriesClustering.ClustData...?

@holgerteichgraeber
Copy link
Owner Author

Does the "reference" data ( test/reference_generation/run_clust.jld2 ) already contain the new Object names based on TimSeriesClustering.ClustData...?

Good call, no it does not. Will have to rerun that I assume.

@holgerteichgraeber
Copy link
Owner Author

holgerteichgraeber commented Aug 27, 2019

Does the "reference" data ( test/reference_generation/run_clust.jld2 ) already contain the new Object names based on TimSeriesClustering.ClustData...?

Fixed in #116 .
Still has the issue that it needs to be rerun sometimes, it fails around 50% of the time. Seems like test cases use much memory overall.

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

2 participants