Closed Bug 1580726 Opened 6 years ago Closed 1 year ago

revisit manifest conditions for reftest

Categories

(Testing :: Reftest, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: egao, Unassigned)

References

Details

Summary

There are many manifest conditions for reftest specified in the manifest.jsm file:
https://searchfox.org/mozilla-central/source/layout/tools/reftest/manifest.jsm#398-576

Some manifest conditions such as skiaContent, azureSkia and azureCairo represent slightly different versions of some condition.

While these may have served a use in the past, it's likely that some of the conditions here no longer serve any useful purpose, but the reftest manifests still carry them since no one has revisited the conditions.

Data

An example push with skiaContent removed from dom/html/reftests/autofocus/reftest.list run on all Windows platforms shows the manifest condition fuzzy-if(skiaContent) serves no actual use.

Version: Version 3 → unspecified
Component: General → Reftest

When removing graphics-related reftest conditions, please ensure you get a review from somebody on the graphics team. Even though conditions may not be used at the moment, they may become relevant again in the future, or may be relevant in some tier-2 or specific configurations when running locally. Having spurious failures appear when running locally is just as undesirable as having extraneous conditions lying around.

/cc lsalzman,jrmuizel as FYI

Severity: normal → minor
Priority: -- → P3
Severity: minor → S4

this has been cleaned up a lot in the last 6 months.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.