Repository navigation
fix(test-optimization): cap screenshot upload retries - #10056
Conversation
A persistent media 5xx bypassed the ordinary retry cap because the upload had a finalization deadline, so the Cypress runner waited until the integration process timed out.
Overall package sizeSelf size: 8.44 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.3.3 | 125.43 kB | 445.14 kB | | opentracing | 0.14.7 | 194.81 kB | 194.81 kB | | dc-polyfill | 0.1.11 | 25.74 kB | 25.74 kB |🤖 This report was automatically generated by heaviest-objects-in-the-universe |
|
BenchmarksBenchmark execution time: 2026-08-28 19:09:20 Comparing candidate commit 5aed405 in PR branch Found 1 performance improvements and 0 performance regressions! Performance is the same for 2295 metrics, 14 unstable metrics.
|
There was a problem hiding this comment.
More details
Screenshot uploads use the normal retry limit when a deadline exists. Final flush requests continue to retry until the deadline.
🤖 Datadog Autotest · Commit 5aed405 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
|
/merge --reason "master is currently red. This PR fixes one of the two issues. This is bypassing 1) CI checks due to the second failure and 2) CODEOWNER review for the owning team" |
|
View all feedbacks in Devflow UI.
You can't provide a reason for skipping checks if you don't skip checks |
|
/merge -f --reason "master is currently red. This PR fixes one of the two issues. This is bypassing 1) CI checks due to the second failure and 2) CODEOWNER review for the owning team" |
|
View all feedbacks in Devflow UI.
Arguments errors:
If you need support, contact us on Slack #devflow with those details! |
Flush worker-exported telemetry before app-closing telemetry snapshots metrics, while leaving retry timers unreferenced so failed endpoints cannot hold the process open. Reuse the merged screenshot retry cap from #10056 because this stacked branch does not yet contain it.
A persistent media 5xx bypassed the ordinary retry cap because the upload had a finalization deadline, so the Cypress runner waited until the integration process timed out.
A persistent media 5xx bypassed the ordinary retry cap because the upload had a finalization deadline, so the Cypress runner waited until the integration process timed out.
A persistent media 5xx bypassed the ordinary retry cap because screenshot uploads have a finalization deadline. Cypress then waited until the integration process timed out.
Screenshot uploads now keep the deadline for cancellation but stop after the ordinary retry cap. Final flush requests continue to retry until their deadline.