Closed Bug 1832532 Opened 1 year ago Closed 1 year ago

GitHub builds unable to parse user.js settings files

Categories

(Testing :: web-platform-tests, defect, P1)

Default
defect

Tracking

(firefox-esr102 unaffected, firefox113 unaffected, firefox114+ fixed, firefox115+ fixed)

RESOLVED FIXED
115 Branch
Tracking Status
firefox-esr102 --- unaffected
firefox113 --- unaffected
firefox114 + fixed
firefox115 + fixed

People

(Reporter: jgraham, Assigned: standard8)

References

(Regression)

Details

(Keywords: regression)

Attachments

(2 files)

Bug 1830265 introduced a backwards-incompatible change into the format of user.js files used to store testing prefs. It also updated mozprofile to allow reading the updated format.

Unfortunately these files are not only used in-tree but also in upstream web-platform-tests. This is currently breaking all the upstream builds (see e.g. this log) and is therefore preventing results being updated on wpt.fyi or on the interop 2023 Dashboard. This is an important public metric that we're tracking, so we need a quick resolution to this problem.

Unfortunately this external usage isn't covered by CI, and it's not expected that everyone understands the details of out-of-tree uses of the code, so the problem was hard to detect before landing.

AFAICT there are two options:

  • We back out the original changeset
  • We do an urgent mozprofile release, so that external tools can get the new code version.

Ideally we'd backout the user.js changes to provide an immediate fix, then release a new mozprofile version, and finally reland the user.js changes once the external systems have a chance to update. That would mean the problem would be fixed as soon as the initial backout reaches central, rather than needing to wait for the mozprofile update to roll out.

Flags: needinfo?(standard8)

Is it just testing/profiles/web-platform/user.js causing the issues, or do the other user.js files do as well? I guess testing/profiles/common/user.js might be another one?

If that's the case, I would propose that we undo the changes to those, and add them to .prettierignore temporarily. Once the dashboard is updated, then we can undo the change.

Flags: needinfo?(standard8) → needinfo?(james)

Everything in https://searchfox.org/mozilla-central/source/testing/profiles/profiles.json#34-40 is used in (some configurations of) web-platform-tests, so I'm not sure there's much advantage in trying to revert specific files vs the entire changeset outside of testing/mozbase.

Flags: needinfo?(james) → needinfo?(standard8)

Ok yeah, everything outside of testing/mozbase/ seems fine then. If I create the backout patch, can you file a bug for the mozprofile update? (I assume that'll need its own bug).

Does the backout also need to go onto 114?

Flags: needinfo?(standard8)

You we are using branches for the non-central builds, so if we can uplift the backout that would be appreciated.

See Also: → 1832541

.prettierignore is not updated here, as unfortunately the exclusion for these files slipped back in during other patches.

Assignee: nobody → standard8
Status: NEW → ASSIGNED

Set release status flags based on info from the regressing bug 1830265

Pushed by mbanner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c65ccc2a49bb Undo prettier formatting changes to testing/profiles/**/user.js until mozprofile is updated. r=jgraham,perftest-reviewers,sparky.

Comment on attachment 9333056 [details]
Bug 1832532 - Undo prettier formatting changes to testing/profiles/**/user.js until mozprofile is updated. r?jgraham!.

Beta/Release Uplift Approval Request

  • User impact if declined: None - This helps to fix the web platform test dashboard.
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: No
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): Not risky as this only reverts a formatting change to some test files.
  • String changes made/needed: None
  • Is Android affected?: No
Attachment #9333056 - Flags: approval-mozilla-beta?
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch

Comment on attachment 9333056 [details]
Bug 1832532 - Undo prettier formatting changes to testing/profiles/**/user.js until mozprofile is updated. r?jgraham!.

Approved for 114 beta 4, thanks.

Attachment #9333056 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: