Skip to content

Re-enable tests on Fuchsia that relied on fml::WriteAtomically #53399

@chinmaygarde

Description

@chinmaygarde

An example of this failure is here. This must be re-enabled once the Fuchsia issue is addressed. The Fuchsia bots were also in quarantine till recently and the last three builds have failed consistently. So it may be that fml::WriteAtomically has not been wired up on Fuchsia or is accessing a directory that is not setup correctly in the test harness. In that case, this may not be a flake. In any case, this issue tracks re-enabling that test.

  • OnServiceProtocolGetSkSLsWorks re-enabled
  • CanLoadSkSLsFromAsset re-enabled
  • CanRemoveOldPersistentCache re-enabled.

Metadata

Metadata

Assignees

Labels

P2Important issues not at the top of the work listc: flakeTests that sometimes, but not always, incorrectly passengineflutter/engine related. See also e: labels.platform-fuchsiaFuchsia code specifically

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions