-
Notifications
You must be signed in to change notification settings - Fork 2.2k
.travis.yml: Don't require FETCH_HEAD (partial fix for failing master tests) #1383
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.yml: Don't require FETCH_HEAD (partial fix for failing master tests) #1383
Conversation
530706f to
cb57341
Compare
|
This commit passes locally, but I expect we need vbatts/git-validation#17 to land before master builds start passing again. |
|
the git-validation upstream has merged now. This PR can be reviewed. |
|
Hold on this. do not review yet |
|
@mrunalp ok. will you restart the travis job to check this it fixed? |
Master builds only have a 'git clone ...' [1] so FETCH_HEAD isn't defined and git-validation crashes [2]. We don't want to be hard-coding a range here, and should update git-validation to handle these cases automatically. Also echo TRAVIS_* variables during testing to make debugging git-validation easier. [1]: https://travis-ci.org/opencontainers/runc/jobs/213508696#L243 [2]: https://travis-ci.org/opencontainers/runc/jobs/213508696#L347 Signed-off-by: W. Trevor King <[email protected]>
cb57341 to
d1fb97f
Compare
|
On Tue, Mar 21, 2017 at 03:24:05PM -0700, Vincent Batts wrote:
@mrunalp ok. will you restart the travis job to check this it fixed?
I bumped the CommitDate to get a new hash and pushed cb57341 → d1fb97f
to trigger Travis. That still won't test “does the new git-validation
work for a post-merge master test?”, but I expect it will (it does for
git-validation's master test [1]). And I can always file a fixup if it
doesn't.
[1]: https://travis-ci.org/vbatts/git-validation/builds/213609902
|
|
Yes
…On Mar 21, 2017 18:53, "Mrunal Patel" ***@***.***> wrote:
@vbatts <https://github.com/vbatts> @wking <https://github.com/wking> Is
this ready for review?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1383 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEF6XsxwuEdtOHboA8N_SZW9LzQ1BpEks5roFTjgaJpZM4MkQPF>
.
|
1 similar comment
|
cool. I think the failure on master https://travis-ci.org/opencontainers/runc/jobs/214004661 is something else? |
|
On Wed, Mar 22, 2017 at 02:18:48PM -0700, Vincent Batts wrote:
I think the failure on master
https://travis-ci.org/opencontainers/runc/jobs/214004661 is
something else?
Yeah. Looks like it was something about TestNotifyMemoryPressure [1].
[1]: https://travis-ci.org/opencontainers/runc/jobs/214004661#L2175
|
|
The |
Master builds only have a
git clone …soFETCH_HEADisn't defined and git-validation crashes. We don't want to be hard-coding a range here, and should update git-validation to handle these cases automatically.Also echo
TRAVIS_*variables during testing to make debugging git-validation easier.