Srinidhi Kaushik <shrinidhi.kaushik@xxxxxxxxx> writes: > Add a new option: "--force-if-includes" to "git-push" where forced > updates are allowed only if the tip of the remote-tracking ref has > been integrated locally, by verifying if the tip of the remote-tracking > ref -- on which a local branch has based on -- is reachable from at > least one of the "reflog" entries of the branch about to be updated > by force on the remote. https://travis-ci.org/github/git/git/jobs/730962458 is a build of 'seen' with this topic, and the same 'seen' without this topic is https://travis-ci.org/github/git/git/builds/730857608 that passes all the jobs. It is curious why one particular job fails while others in the same build is OK. I've seen this pattern for this topic in the past few days. The failure in t5533-push-cas.sh is sort-of understandable as the topic directly touches the area of the code the failing test exercises, but the failure in t3701 is totally unexpected. You can go down to the bottom of the page and click on the ci/print-test-failures.sh line to see which test piece fails. Anything rings a bell? Thanks.
