docker, runtime: only build clang and llc targets#10956
Conversation
|
test-me-please |
197e4cb to
1661e19
Compare
|
test-me-please EDIT: failure looks like #10882 https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/18735/ |
Specify only the targets we need from the llvm build, namely `clang` and `llc`. This reduces the amount of objects to build by ~300 and thus also reduces build time a bit. Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
1661e19 to
d77ff8b
Compare
|
test-me-please |
|
test-me-please |
1 similar comment
|
test-me-please |
|
Hit #10838 |
|
test-me-please |
|
test-me-please EDIT: hit #10929 again https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/18792/ |
|
restart-ginkgo EDIT: hit #10929 again https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/18806/ |
|
test-with-kernel |
|
test-gke |
|
restart-ginkgo EDIT: net-next vm provisioning failure https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/18814/ |
|
restart-ginkgo |
2 similar comments
|
restart-ginkgo |
|
restart-ginkgo |
After updating the cilium-runtime image we also get a newer bpftool build which generates a bpf_features.h header that includes the netns cookie and therefore on bpf-next kernel we must fail this particular test. Similarly, doFragmentedRequest() from pod loopback does not make sense either anymore. Given we performed the earlier testCurlRequestFail() for a service, there is no point in retesting a fragmented request again for this address. Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
024cead to
06b1501
Compare
|
test-me-please |
|
Did you create a PR for cilium/packer-ci-build to cache the updated Docker image in the CI VM images? |
This will pull in Go 1.14.2 via cilium/cilium#10912 and the build llvm changes from cilium/cilium#10956 Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
This will pull in Go 1.14.2 via cilium/cilium#10912 and the build llvm changes from cilium/cilium#10956 Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
@brb Thanks for the reminder. Opened PR cilium/packer-ci-build#208 |
This will pull in Go 1.14.2 via cilium/cilium#10912 and the build llvm changes from cilium/cilium#10956 Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Specify only the targets we need from the llvm build, namely `clang` and `llc`. This reduces the amount of objects to build by ~300 and thus also reduces build time a bit. Same as cilium/cilium#10956 Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Specify only the targets we need from the llvm build, namely `clang` and `llc`. This reduces the amount of objects to build by ~300 and thus also reduces build time a bit. Same as cilium/cilium#10956 Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Specify only the targets we need from the llvm build, namely `clang` and `llc`. This reduces the amount of objects to build by ~300 and thus also reduces build time a bit. Same as cilium/cilium#10956 Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Specify only the targets we need from the llvm build, namely
clangandllc. This reduces the amount of objects to build by ~300 and thusalso reduces build time a bit.
(Edit from @borkmann: added the test update commit which fixes below issue)
Fixes: #10882