PMM-14912-dynamic-thresholds (FB)

[matejkubinec]

Custom branches:

• pmm
• grafana

[JNKPercona]

Looks like there are outdated source branches.
Please update them and restart the job
percona/grafana#912

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4449-2d45cbd
Client docker: perconalab/pmm-client-fb:PR-4449-2d45cbd
Watchtower docker: perconalab/pmm-watchtower-fb:PR-4449-2d45cbd
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-2d45cbd.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4449-2d45cbd&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-2d45cbd.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/6665/

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4449-819cb70
Client docker: perconalab/pmm-client-fb:PR-4449-819cb70
Watchtower docker: perconalab/pmm-watchtower-fb:PR-4449-819cb70
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-819cb70.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4449-819cb70&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-819cb70.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/6837/

[JNKPercona]

Looks like there are outdated source branches.
Please update them and restart the job
percona/pmm#5579

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4449-9fd35fe
Client docker: perconalab/pmm-client-fb:PR-4449-9fd35fe
Watchtower docker: perconalab/pmm-watchtower-fb:PR-4449-9fd35fe
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-9fd35fe.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4449-9fd35fe&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-9fd35fe.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/6869/

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4449-a3b42b0
Client docker: perconalab/pmm-client-fb:PR-4449-a3b42b0
Watchtower docker: perconalab/pmm-watchtower-fb:PR-4449-a3b42b0
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-a3b42b0.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4449-a3b42b0&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-a3b42b0.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/6872/

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4449-b669d75
Client docker: perconalab/pmm-client-fb:PR-4449-b669d75
Watchtower docker: perconalab/pmm-watchtower-fb:PR-4449-b669d75
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-b669d75.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4449-b669d75&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-b669d75.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/6875/

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4449-f80b7c8
Client docker: perconalab/pmm-client-fb:PR-4449-f80b7c8
Watchtower docker: perconalab/pmm-watchtower-fb:PR-4449-f80b7c8
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-f80b7c8.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4449-f80b7c8&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-f80b7c8.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/6876/

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4449-3256b5e
Client docker: perconalab/pmm-client-fb:PR-4449-3256b5e
Watchtower docker: perconalab/pmm-watchtower-fb:PR-4449-3256b5e
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-3256b5e.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4449-3256b5e&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-3256b5e.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/6894/

[JNKPercona]

Looks like there are outdated source branches.
Please update them and restart the job
percona/pmm#5579
percona/grafana#912

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4449-3eded28
Client docker: perconalab/pmm-client-fb:PR-4449-3eded28
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-3eded28.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4449-3eded28&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-3eded28.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/7222/

[travagliad]

The red @fb-alerting|@fb-settings UI tests check on this PR reproduced, and it is a pmm-qa test bug, not a problem with your change — nothing here needs fixing on your side. All 13 actionable failures are in codeceptjs-e2e/tests/ia/ruleTemplates_test.js and share one cause: the rule-template row-action locators address a template via //td[contains(text(), "NAME")], and the new Name-column Cell renderer in percona/grafana#912 moves the name into <td><div><span>NAME</span></div></td> — XPath text() only sees a node's direct text children, so every lookup by name matches nothing.

Verified on a throwaway VM running this PR's own build perconalab/pmm-server-fb:PR-4449-3eded28: against the live table the current locator returns 0 matches and a row-scoped contains(.) one returns 1, and the suite goes from 13 passed, 13 failed to 26 passed, 0 failed with only the locators changed.

Fix: percona/pmm-qa#1297. It matches both DOM shapes (re-verified green on perconalab/pmm-server:3-dev-latest too), so it is not blocked on grafana#912 and needs no coordination with your merge. Once it lands, this check should go green on your next FB build.

---

Generated by Claude Code

[JNKPercona]

Looks like there are outdated source branches.
Please update them and restart the job
percona/grafana#912

[JNKPercona]

Looks like there are outdated source branches.
Please update them and restart the job
percona/pmm#5878

[JNKPercona]

Server docker: perconalab/pmm-server-fb:PR-4449-273677e
Client docker: perconalab/pmm-client-fb:PR-4449-273677e
Client tarball: https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-273677e.tar.gz
Staging instance: https://pmm.cd.percona.com/job/pmm3-aws-staging-start/parambuild/?DOCKER_VERSION=perconalab/pmm-server-fb:PR-4449-273677e&CLIENT_VERSION=https://s3.us-east-2.amazonaws.com/pmm-build-cache/PR-BUILDS/pmm-client/pmm-client-PR-4449-273677e.tar.gz

[JNKPercona]

API tests have succeded: https://pmm.cd.percona.com/job/pmm3-api-tests/7354/

[travagliad]

Both red checks on run 34601581070 were looked at, and neither is caused by your change — I re-ran the failed jobs and both came back green (helm-tests success, @pmm-ps-integration success with its tests actually executing and passing).

Helm tests failed on a transient external error, not on PMM: helm show values --version 1.4.0 percona/pmm got a 500 Internal Server Error fetching pmm-1.4.0.tgz from GitHub release assets. That URL serves 200 again, the chart is intact in the index, the same command ran 20/20 clean on a throwaway VM, and helm-tests has been green on pmm-qa main for ten consecutive scheduled runs including the one 12 hours before yours. Nothing to fix.

@pmm-ps-integration is a pmm-qa CI problem that predates this PR. The job provisions two PS clusters (six package-based MySQL installs, one node at a time) before any test runs, and on slow runners that setup takes 43.8–57.2 min against a 60 min job timeout — so the job gets killed in provisioning and the tests never run. It hit 57 min on your run; seven of the ten FB runs before yours, across six different branches, died the same way, and only one of ten ever executed the suite. The same setup completes in 9m37s on an uncontended VM and took 8m24s on your re-run, so it is apt/mirror throughput on the runners, not PMM and not the tests.

Fix for the timeout: percona/pmm-qa#1413. Nothing is needed from you on either check.

---

Generated by Claude Code

[travagliad]

Correction to my earlier note: the verdict for your PR is unchanged (both failures were environmental, nothing needed from you), but the fix I linked, percona/pmm-qa#1413, is closed — its diagnosis was wrong.

I had attributed the 43.8–57.2 min setups to apt throughput on busy runners and raised the job timeout. That does not hold: an FB run on 09-10 at 07:43 UTC did the same setup in 9m14s on the same pmm-qa commit and the same runner image. The slowness is degraded network egress on individual runner VMs — in one run here @pmm-ps-integration finished setup in 7m23s while @ssl-postgres spent 50 min in the same step, and re-running the latter an hour later took 2m27s.

The real exposure is that each job re-downloads ~1.43 GB of identical packages (once per each of 5 containers), so a slow VM turns a 35-second download into hours. Sharing that cache is the actual fix and is what I will pursue instead of a bigger timeout.

---

Generated by Claude Code