Related to #17420
Added developer note to minimize issues related to Travis CI accounts.
Related to #17420
Added developer note to minimize issues related to Travis CI accounts.
460 | @@ -461,6 +461,8 @@ General Bitcoin Core 461 | - *Explanation*: If the test suite is to be updated for a change, this has to 462 | be done first. 463 | 464 | + - ***Developers using their own Travis CI account*** to pretest their commits should work off of a recent master that is passing. This ensures that your work is based on a passing version and any fails are contained within your commit. ***You may have to restart your builds. See: [Build Timeouts](https://docs.travis-ci.com/user/customizing-the-build#build-timeouts)***
Adding *** around this is overkill, it is not significantly more important than the other recommendations. Please format this like the other items.
Please add this documentation to the existing one in the .travis.yml. It is not relevant for anyone not using travis.
I appreciate the feedback - thank you.
Please add this documentation to the existing one in the .travis.yml. It is not relevant for anyone not using travis.
Arguably that particular item in the developer notes "Make sure pull requests pass Travis CI before merging." is about Travis. But ok, better to put the documentation closer to where someone might notice it.
This collides 100% with #17420 now, though. Would be better to review that and suggest improvements there.
developer notes "Make sure pull requests pass Travis CI before merging."
That should probably be removed then.
Or remove "Travis". it's still important to have the CI passing before merge, to prevent it from failing on the branch. As is happening for Appveyor, yet again.
As with the appveyor failure right now, there is often no way for a contributor to make sure the ci passes. The issue might be unrelated to their changes.
It should probably say that the unit and functional tests should pass locally.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
Thanks for the feed back. I believe a few strategic changes can reduce frustration for members and contributors. I think prompting contributors to rebase (if needed) prior to creating a PR can further streamline this a little. Clearly #17420 should be merged first - I can always add language about rebasing after that.
I also put in a feature request with Travis CI to warn about upstream failures on a topic branch. Maybe they will solve that part of the issue in the future upgrade?