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.

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

[On Hold] too many emails from Travis CI #322

Closed
jGaboardi opened this issue Oct 21, 2019 · 2 comments
Closed

[On Hold] too many emails from Travis CI #322

jGaboardi opened this issue Oct 21, 2019 · 2 comments
Assignees
@jGaboardi
Labels
on hold
Milestone
future release

Comments

@jGaboardi
Copy link
Member

jGaboardi commented Oct 21, 2019 •
edited
Loading

Although there doesn't seem to be a reliable fix for this at the moment, we should continue to follow developments. The allowed_failures and fast_finish options seem to be the culprits.

@sjsrey @ljwolf
@jGaboardi jGaboardi added this to the future release milestone Oct 21, 2019
@jGaboardi jGaboardi self-assigned this Oct 21, 2019
@jGaboardi jGaboardi changed the title too many email from Travis CI too many emails from Travis CI Oct 21, 2019
jGaboardi added a commit to jGaboardi/spaghetti that referenced this issue Nov 27, 2019
@jGaboardi
removing fast finish to address pysal#322
920ff65
@jGaboardi jGaboardi mentioned this issue Nov 27, 2019
Merged
@jGaboardi
Copy link
Member Author

This is patched in #335, but will put "On Hold" until a real solution is found.

@jGaboardi jGaboardi changed the title too many emails from Travis CI [On Hold] too many emails from Travis CI Nov 27, 2019
@jGaboardi jGaboardi mentioned this issue Feb 17, 2020
Merged
@jGaboardi
Copy link
Member Author

There is no actual need for fastfinish. Closing for now. We can reopen later if interested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jGaboardi jGaboardi

Labels
on hold
Projects
None yet
Milestone
future release
Development

No branches or pull requests
1 participant
@jGaboardi