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: Revert "Run extended tests once daily" #15328

Merged
merged 1 commit into from Feb 4, 2019

Conversation

@MarcoFalke
Copy link
Member

@MarcoFalke MarcoFalke commented Feb 2, 2019

Now that the extended tests are only pruning and dbcrash, both which are too long [1] to run on travis, we can revert this commit. All tests other than those two are still run for every travis pull request or cron run.

[1] https://travis-ci.org/bitcoin/bitcoin/jobs/487615211#L2930

@laanwj
Copy link
Member

@laanwj laanwj commented Feb 2, 2019

It's really too bad that those tests cannot run on Travis, even if it's only two tests it's useful to run them every day.

@MarcoFalke
Copy link
Member Author

@MarcoFalke MarcoFalke commented Feb 2, 2019

An alternative would be to exclude the unit test in the cron job

@laanwj
Copy link
Member

@laanwj laanwj commented Feb 4, 2019

utACK anyhow, this can always be restored when there is a point

MarcoFalke added a commit to MarcoFalke/bitcoin-core that referenced this issue Feb 4, 2019
fa6b7b9 travis: Revert "Run extended tests once daily" (MarcoFalke)

Pull request description:

  Now that the extended tests are only pruning and dbcrash, both which are too long [1] to run on travis, we can revert this commit. All tests other than those two are still run for every travis pull request or cron run.

  [1] https://travis-ci.org/bitcoin/bitcoin/jobs/487615211#L2930

Tree-SHA512: dff293823336677380f6e804379125687869a4b547c968f0b6aae80daee1cbca2cfb845b63de7135f31fbe2383d8d7654694b6dc8a6a6b7d02d57ee8ff107527
@MarcoFalke MarcoFalke merged commit fa6b7b9 into bitcoin:master Feb 4, 2019
2 checks passed
@MarcoFalke MarcoFalke deleted the Mf1902-travisExt branch Feb 4, 2019
@MarcoFalke
Copy link
Member Author

@MarcoFalke MarcoFalke commented Feb 4, 2019

We never have been running pruning and dbrash would always time out, so at least now it is explicit that we don't run them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants