chore(deps): update docker.elastic.co/wolfi/chainguard-base:latest docker digest to aad4cd4 - autoclosed

[elastic-renovate-prod]

This PR contains the following updates:

Package	Type	Update	Change
docker.elastic.co/wolfi/chainguard-base		digest	c16d3ad -> aad4cd4
docker.elastic.co/wolfi/chainguard-base	final	digest	c16d3ad -> aad4cd4

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[xrmx]

@elastic/observablt-robots Hey, do you know if we have a way to make the job fail instead of getting stuck waiting for status? Thanks

[v1v]

@elastic/observablt-robots Hey, do you know if we have a way to make the job fail instead of getting stuck waiting for status? Thanks

Do you mean the required GH check buildkite/docs-build-pr?

[xrmx]

@elastic/observablt-robots Hey, do you know if we have a way to make the job fail instead of getting stuck waiting for status? Thanks

Do you mean the required GH check buildkite/docs-build-pr?

Yes

[xrmx]

Cool, now getting coverage reports stopped working 😓

[v1v]

I understand that building/docs-build-pr should always run; if it does not run, then the Platform Productivity team might need to be involved or docs teams. That's a pipeline outside of our control

You can force that check to run with the GitHub command run docs-build

[xrmx]

I understand that building/docs-build-pr should always run; if it does not run, then the Platform Productivity team might need to be involved or docs teams. That's a pipeline outside of our control

You can force that check to run with the GitHub command run docs-build

Yeah, was wondering if it was possible to configure github to report failure after a timeout instead of waiting for something, but no big deal. Thanks for the answer.

[v1v]

Yeah, was wondering if it was possible to configure github to report failure after a timeout instead of waiting for something, but no big deal. Thanks for the answer.

As far as I know, that's not possible. Mandatory GitHub checks are always shown, and if the CI runs for that GH action, it will report the status (running, failed, success).

In the case you mentioned, it didn't even run. Hence, the GH check was waiting; since it runs in Buildkite and uses some bot to orchestrate those things, I don't know much, but maybe there will be no retry if the GitHub event was not processed or lost. If you see this often, we can ask the Platform team if they are aware of any issues

[v1v]

@xrmx , I've just found a PR that improves the speed for the the docs GitHub check for the APM Server, maybe we can do something similar. I'll bump this conversation with the different system owners and see whether we can come up with some strategy

[xrmx]

@xrmx , I've just found a PR that improves the speed for the the docs GitHub check for the APM Server, maybe we can do something similar. I'll bump this conversation with the different system owners and see whether we can come up with some strategy

That would be great