-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
s2i bump #12237
s2i bump #12237
Conversation
[testextended][extended:core(builds|image_ecosystem)] |
[test] |
@jim-minter assuming this passes tests now, ptal. particularly where i had to change to use CreateTarStream instead of StreamFileAsTarWithCallback |
t := stitar.New() | ||
err := t.StreamFileAsTarWithCallback(src, filepath.Base(dest), uploader, nullWalkFunc, false) | ||
t := s2itar.New(s2iutil.NewFileSystem()) | ||
err := t.CreateTarStream(src, false, uploader) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
err := t.CreateTarStream(src, false, uploader)
should read:
tarWriter := s2itar.RenameAdapter{Writer: tar.NewWriter(uploader), Old: filepath.Base(src), New: filepath.Base(dest)}
err := t.CreateTarStreamToTarWriter(src, true, tarWriter, nil)
if err == nil {
err = tarWriter.Close()
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only close tarWriter if err is nil?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's the best I could think of - tarWriter.Close() writes the terminating '\0's record which is supposed to indicate to tar that its stream isn't erroneously truncated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that code is a copy/paste of the equivalent that I implemented in s2i
@bparees bar the above change, looks fine to me. |
@jim-minter it seems plausible the latest s2i changes broke extended builds in origin... (see latest extended test failures) |
seems like the permissions aren't getting set properly on the assemble-runtime script... investigating. |
@php-coder it looks like the scripts in your test repo are not marked executable: I guess this used to work, but would you expect it to work? |
prereq PRs (I think): |
@bparees Thank you, Ben! It works before but now I don't know how :-/ |
I think our Tar logic may have been updating the permissions. |
still failing :(
I assume it has to do w/ this change in s2i: And that we are now not going through the same chmod path. |
My bad. I'm hoping that openshift/source-to-image#662 will fix this, but I'm still testing it here. |
Confirmed, with this PR + openshift/source-to-image#662, the extended case 'should use assemble-runtime script from URL' now works for me. @php-coder I don't mind either way but I would be tempted to revert openshift/test-maven-app#1 and openshift/test-maven-app#2, FWIW. |
@jim-minter You want to revert them just to make sure that your fix is working? |
@php-coder shouldn't be necessary, since we're still broken right now (pending @jim-minter's changes), so we should already know if his changes fix it. |
@bparees Ok. Just in case I invited you and @jim-minter to be collaborators in this repo, so you will be able to do any changes that may be required. I don't want to block you. |
@php-coder thanks! |
Evaluated for origin testextended up to f99d782 |
flake #10663 |
Evaluated for origin test up to f99d782 |
continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/12465/) (Base Commit: 7061e0b) |
continuous-integration/openshift-jenkins/testextended SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin_extended/924/) (Base Commit: 7061e0b) (Extended Tests: core(builds|image_ecosystem)) |
[merge]
Ben Parees | OpenShift
…On Dec 16, 2016 4:45 PM, "OpenShift Bot" ***@***.***> wrote:
continuous-integration/openshift-jenkins/testextended SUCCESS (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin_extended/924/)
(Base Commit: 7061e0b
<7061e0b>)
(Extended Tests: core(builds|image_ecosystem))
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12237 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEvl3uww0HOOK2FKRQmBdFWdo5rDEGZsks5rIwZ9gaJpZM4LLKZM>
.
|
flake #9886 |
Evaluated for origin merge up to f99d782 |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/12474/) (Base Commit: 48b0a74) (Image: devenv-rhel7_5563) |
@jim-minter ptal