THROWAWAY: fold pg_upgrade coverage into every test job leg (do not merge) - #48
Conversation
…experiment) Instead of a separate 2-leg pg-upgrade-test job (old_pg 10/12 -> 18), have every leg of the test job's own PG matrix binary-pg_upgrade its cluster to the newest supported major (10-17 -> 18; the 18 leg itself skips it) using the container it already has. Removes the now-fully-subsumed standalone pg-upgrade-test job. Purely to measure real CI runner-minutes/wall-clock for this approach against the current baseline - not intended to merge. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Throwaway CI-cost experiment - data collected (see follow-up report to maintainer). Closing without merging per plan; deleting the branch next. |
1 participant
Experiment only, not intended to merge (will close + delete branch once data is collected).
Instead of the standalone 2-leg pg-upgrade-test job (old_pg 10/12 -> new_pg 18, its own containers), every leg of the test job's own PG matrix (10-18) now also binary-pg_upgrades its cluster to the newest supported major (18) as a final set of steps, reusing the container/checkout/install that leg already did - full "every supported major -> 18" coverage (7 upgrade legs: 10-17, vs. 2 today) instead of a small sample. The 18 leg itself skips those steps (nothing newer to upgrade to). The now-fully-subsumed standalone pg-upgrade-test job is removed.
Goal is to measure real runner-minutes (primary) and wall-clock (secondary, noisy due to this org's shared concurrent-job ceiling) for this topology against the current baseline (test matrix + separate pg-upgrade-test job), to decide whether the added coverage is worth adopting for real.