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

main: default travis commit range is unreliable #15

Merged
merged 1 commit into from
Mar 21, 2017
Merged

Conversation

vbatts
Copy link
Owner

@vbatts vbatts commented Mar 21, 2017

opencontainers/runc#1378 (comment)
points to an alternate approach.

Reported-by: Mrunal Patel mrunalp@gmail.com
Signed-off-by: Vincent Batts vbatts@hashbangbash.com

opencontainers/runc#1378 (comment)
points to an alternate approach.

Reported-by: Mrunal Patel <mrunalp@gmail.com>
Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
@vbatts
Copy link
Owner Author

vbatts commented Mar 21, 2017

passes

@vbatts vbatts merged commit a23edf1 into master Mar 21, 2017
@vbatts vbatts deleted the fix_range_var branch March 21, 2017 13:50
wking added a commit to wking/runc that referenced this pull request Mar 21, 2017
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
[3]: vbatts/git-validation#15

Signed-off-by: W. Trevor King <wking@tremily.us>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant