You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tag pushrebase Scuba with land_instance_id for MR QE terminal-bounce readout
Summary:
The merge-resolution QE needs the ITT *terminal* conflict-bounce (true-rescue) rate, test vs control, computed retry-inclusively. That terminal outcome has to be grouped per land across the Landcastle/Sandcastle client rebase-retry loop, but no existing column on `mononoke_land_service` is stable across that loop: `session_uuid`/`client_correlator` are per push-invocation, `sandcastle_nonce` is per job-type, and `changeset_id` changes on rebase.
This adds a stable per-land grouping key -- the Sandcastle land instance id -- to the pushrebase Scuba samples, mirroring how `mr_qe_arm` is stamped (D108612592). The readout then groups `mononoke_land_service` by `land_instance_id` to roll a land's attempts up to a single terminal outcome and slice by arm -- entirely within source_control-owned tables (no www logger / cross-team change).
- Landcastle (`LandcastleMrQeBuckets`) emits a `LAND_INSTANCE_ID` pushvar (the Sandcastle instance id) on every (re)push of an enrolled land; the same Sandcastle instance drives the whole `genPush` retry loop, so all attempts of a land carry the same value.
- Mononoke reads it into `PushrebaseFlags.land_instance_id` (UTF-8 decode at the bookmarks_movement boundary so `metaconfig_types` stays bytes-free) and stamps `land_instance_id` in the `do_pushrebase_bonsai` `with_mutated_scuba` rebind, so every downstream sample inherits it.
Observability only; absent/`None` for out-of-experiment traffic; no behavior change.
Reviewed By: YousefSalama, lmvasquezg
Differential Revision: D110041743
fbshipit-source-id: f02137439376731a582cc1275c1110ee0f5374d4
0 commit comments