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
[release-4.6] Bug 1920626: add test to verify build /run fs contents #25838
[release-4.6] Bug 1920626: add test to verify build /run fs contents #25838
Conversation
@gabemontero: Bugzilla bug 1920626 is in a bug group that is not in the allowed groups for this repo.
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
GCE IAM create issues e2e-gcp-builds /test e2e-gcp-builds |
OK e2e-gcp-builds has passed ... that is the e2e we've updated with this PR. /bugzilla refresh |
@gabemontero: Bugzilla bug 1920626 is in a bug group that is not in the allowed groups for this repo.
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest |
/assign @adambkaplan @jwforres FYI in case the window for this week is still open this PR is the new e2e's for openshift/builder#211 and openshift/builder#212 which you approved yesterday does anybody know why the bugzilla bot will not add the usual labels for this one ... I don't follow the message provided. thanks |
will message you on slack. |
OK @adambkaplan @bparees the e2e-gcp-builds with our new tests pass in 4.6 as well please review / tag with lgtm / approve as you deem fit the only difference from the 4.7 PR was that Clayton's |
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.
nits, otherwise looks good.
hasRightListing := false | ||
if strings.Contains(logs, lsRSlashRun) || strings.Contains(logs, lsRSlashRunFIPS) { | ||
hasRightListing = true | ||
} |
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.
nit - can't this be one statement?
hasRightListing := false | |
if strings.Contains(logs, lsRSlashRun) || strings.Contains(logs, lsRSlashRunFIPS) { | |
hasRightListing = true | |
} | |
hasRightListing := strings.Contains(logs, lsRSlashRun) || strings.Contains(logs, lsRSlashRunFIPS) |
spec: | ||
runPolicy: Serial | ||
source: | ||
dockerfile: "FROM %s\nRUN chmod -R uga+rwx /run\nUSER 1001" |
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.
nit - can we use multiline YAML syntax?
dockerfile: "FROM %s\nRUN chmod -R uga+rwx /run\nUSER 1001" | |
dockerfile: | | |
FROM %s | |
RUN chmod -R uga+rwx /run | |
USER 1001" |
spec: | ||
runPolicy: Serial | ||
source: | ||
dockerfile: "FROM %s\nRUN ls -R /run\nUSER 1001" |
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.
nit - use multiline YAML
dockerfile: "FROM %s\nRUN ls -R /run\nUSER 1001" | |
dockerfile: | | |
FROM %s | |
RUN ls -R /run | |
USER 1001" |
/lgtm Since the code already merged in 4.7, can follow up with my nits later. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan, gabemontero The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherrypick release-4.5 |
@gabemontero: #25838 failed to apply on top of branch "release-4.5":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
manual pick of #25810
see #25829 (comment) and #25829 (comment) for the "why"