Kubekins-e2e fails to run a bazel build when wrapped by runner.sh #18706
Assignees
Labels
area/images
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Comments
|
May be related to: #18604 |
|
is this fixed after #18735 ? |
|
@BenTheElder I believe it should be, but will leave it to @michaelmdresser to confirm |
|
I'm encountering the same error using |
|
but not with an older image?
…On Tue, Aug 11, 2020 at 2:41 PM Michael Dresser ***@***.***> wrote:
I'm encountering the same error usingimage:
gcr.io/k8s-testimages/kubekins-e2e:v20200811-4afd9ba-master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18706 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHADKZ7QKTJMBPXMB3PBG3SAG3IHANCNFSM4PW2TEQA>
.
|
|
From what I recall, doing roughly this with an older image (~1 month ago) used to work. The two images notes in this issue definitely are not working. I can try this with a further back image if you'd like to see the results. |
|
If we regressed on this we should fix it, I'm wondering if there's
something else going on though ...
we use runner.sh and bazel in this image in CI I thought ...
…On Tue, Aug 11, 2020 at 3:18 PM Michael Dresser ***@***.***> wrote:
From what I recall, doing roughly this with an older image (~1 month ago)
used to work. The two images notes in this issue definitely are not
working. I can try this with a further back image if you'd like to see the
results.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18706 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHADK4D2YZUUWXZHEUEQGTSAG7UJANCNFSM4PW2TEQA>
.
|
|
@michaelmdresser can you please share logs when run using latest image? i explicitly tested this scenario by hand last friday. |
|
My |
|
I found these logs for the latest container from before my Container logs: Running |
BenTheElder
added
area/images
priority/important-soon
|
FYI this is still reproducible doesn't work does |
in the error we see: I think we need SOURCE_DATE_EPOCH to not propagate to this part of the bazel build and / or we need to ensure that it's valid or unset. |
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
k8s-ci-robot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
k8s-ci-robot
added
lifecycle/rotten
BenTheElder
removed
the
lifecycle/rotten
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
When running a
bazel buildcommand as part of a prow job spec (testing with mkpod/mkpj deploying to a GKE cluster), it fails buildingpython-gflags. When the command is not wrapped byrunner.sh, it works fine.What you expected to happen:
The build should complete without incident.
How to reproduce it (as minimally and precisely as possible):
Write a periodic job spec like so:
Use
mkpj.sh --job="minimal-reproduce-bazel-failure > pj.yaml. Thenmkpod --prow-job="pj.yaml" > pod.yaml.Generated pod spec:
Deploy to a cluster with:
kubectl apply -f pod.yaml.Watch logs with
kubectl. Observe the following error output:Also reproducible with exec. Replace the container args with some wait or infinite tail, then use exec for the same result:
kubectl exec -it PODNAME -- runner.sh /bin/bash -c 'git clone https://github.com/kubernetes/cloud-provider-gcp; cd cloud-provider-gcp; bazel build //release:release-tars'Please provide links to example occurrences, if any:
Anything else we need to know?:
Running the commands without
runner.shsucceeds without incident. Also, I have spent quite a bit of time doing nearly this exact same process with presubmit jobs without incident. I'm not sure if this some quirk of job spec generation. This issue does not occur when usinggcr.io/k8s-testimages/krte:v20200726-f8d6253-1.16as the container and replacingrunner.shwithwrapper.sh.The text was updated successfully, but these errors were encountered: