Skip to content

Fix the timeout error on Travis #11640

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Nov 15, 2018
Merged

Fix the timeout error on Travis #11640

merged 1 commit into from
Nov 15, 2018

Conversation

taehoonlee
Copy link
Contributor

Summary

This PR tries to fix the timeout error on Travis based on the lessons learned in #10929.

Related Issues

PR Overview

  • This PR requires new unit tests [y/n] (make sure tests are included)
  • This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
  • This PR is backwards compatible [y/n]
  • This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

@taehoonlee
Copy link
Contributor Author

@fchollet, maybe this PR is one of the temporary solutions for the recent build errors.

fchollet
fchollet approved these changes Nov 15, 2018
View reviewed changes
Copy link
Collaborator

@fchollet fchollet left a comment

Choose a reason for hiding this comment

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

Ha, multiprocessing, the bane of CI.

@fchollet fchollet merged commit 8b59e31 into keras-team:master Nov 15, 2018
@taehoonlee taehoonlee deleted the fix_ci_1 branch November 16, 2018 00:12
kiku-jw pushed a commit to kiku-jw/keras that referenced this pull request Mar 4, 2019
@taehoonlee @kiku-jw
Fix the timeout error on Travis (keras-team#11640)
1f1aae7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fchollet fchollet fchollet approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@taehoonlee @fchollet