search

falcosecurity / test-infra

Falco workflow & testing infrastructure
https://prow.falco.org
Apache License 2.0
31 stars 110 forks source link

Failing build-new-drivers-amazonlinux2-presubmit #747

Closed mcbarzi closed 1 year ago

mcbarzi commented 2 years ago

Which jobs are failing: seeing this error in the job https://prow.falco.org/view/s3/falco-prow-logs/pr-logs/pull/falcosecurity_test-infra/742/build-new-drivers-amazonlinux2-presubmit/1541688127691689984

Which test(s) are failing:

359.amzn2.x86_64_1.o)
utils/checkfiles config/39ae7d40496793cf3d3e7890c9bbdc202263836b/amazonlinux2_4.14.275-207.503.amzn2.x86_64_1.yaml
DRIVERKIT=/bin/driverkit S3_DRIVERS_BUCKET="falco-distribution" S3_DRIVERS_KEY_PREFIX="driver" SKIP_EXISTING=true utils/build config/39ae7d40496793cf3d3e7890c9bbdc202263836b/amazonlinux2_4.14.275-207.503.amzn2.x86_64_1.yaml
INFO using config file                             file=config/39ae7d40496793cf3d3e7890c9bbdc202263836b/amazonlinux2_4.14.275-207.503.amzn2.x86_64_1.yaml
INFO driver building, it will take a few seconds   processor=docker
FATA exiting                                       error="\"specify container image platform\" requires API version 1.41, but the Docker daemon API version is 1.38"
utils/checkfiles config/39ae7d40496793cf3d3e7890c9bbdc202263836b/amazonlinux2_4.14.243-185.433.amzn2.x86_64_1.yaml

Since when has it been failing:

Test link: https://github.com/falcosecurity/test-infra/pull/742 Reason for failure:

Anything else we need to know:

maxgio92 commented 2 years ago

Hey @mcbarzi thanks for pointing that out. #743 already fixed this issue. BTW in the meantime we can retry the job.

maxgio92 commented 2 years ago

@mcbarzi @maria-barcena-phx you can keep posted, here the job status.

FedeDP commented 2 years ago

It is now up on download.falco.org! Sorry for the inconvenience :) There has been quite a bit of work on driverkit and test-infra to support multi architectures (arm64) drivers builds, and a bug slipped in!

maxgio92 commented 2 years ago

I think this can be closed now @mcbarzi

poiana commented 1 year ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

poiana commented 1 year ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

poiana commented 1 year ago

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community. /close

poiana commented 1 year ago

@poiana: Closing this issue.

In response to [this](https://github.com/falcosecurity/test-infra/issues/747#issuecomment-1329789001): >Rotten issues close after 30d of inactivity. > >Reopen the issue with `/reopen`. > >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Provide feedback via https://github.com/falcosecurity/community. >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.