Skip to content

full_coverage_test is flaky on Windows and Linux #23848

Closed
@whesse

Description

@whesse

standalone/full_coverage_test is failing flakily on win32 release since 868d2c6 Mon Jul 13 17:49:49 2015 -0700
It also fails on win64 release.

Marking it as flaky in tests/standalone/standalone.status.

This test is also using package:unittest, which the core tests in tests/core, tests/standalone/, tests/language, tests/compiler, and tests/lib (except async?) should not be dependent on.
It should be rewritten not to use it - not many changes are needed.

FAILED: none-vm-checked release_x64 standalone/full_coverage_test
Expected: Pass
Actual: RuntimeError
CommandOutput[vm]:

stdout:
unittest-suite-wait-for-done
FAIL: CoverageTests
Expected: <0>
Actual: <3>

package:unittest/src/simple_configuration.dart 128:34 SimpleConfiguration.onExpectFailure
package:unittest/src/simple_configuration.dart 24:13 _ExpectFailureHandler.fail
package:unittest/src/matcher/expect.dart 121:5 DefaultFailureHandler.failMatch
package:unittest/src/matcher/expect.dart 95:20 expect
tests\standalone\full_coverage_test.dart 96:5 generateCoverage
tests\standalone\full_coverage_test.dart 219:5 main.
package:unittest/src/internal_test_case.dart 120:37 InternalTestCase.run.
....

@fsc8000 @mlippautz @kodandersson

Metadata

Metadata

Assignees

Labels

P2A bug or feature request we're likely to work onarea-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.os-windows

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions