mirror of
https://github.com/dart-lang/sdk
synced 2024-09-16 01:21:07 +00:00
744231d16e
It seems to me that this test doesn't provide value for the JS backends. The test was first introduced 11 years ago to investigate and fix GC issues in Dartium that happened across the Dart/DOM boundary (see https://github.com/dart-lang/sdk/issues/1448). While the test works in many configurations, this test is flaky in dart2js-firefox (37%) and DDC (8-14%). I haven't investigated the reasons behind the timeouts, but given the origins of the test, it doesn't seem worth fixing it. Change-Id: I3eaf2273209b587ce5ecfcf4a2bbbd9cb8b990fc Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/332167 Reviewed-by: Stephen Adams <sra@google.com> Commit-Queue: Sigmund Cherem <sigmund@google.com> |
||
|---|---|---|
| .. | ||
| analyzer | ||
| async | ||
| collection | ||
| convert | ||
| developer | ||
| fix_data_tests | ||
| html | ||
| isolate | ||
| js | ||
| js_interop_unsafe | ||
| math | ||
| mirrors | ||
| typed_data | ||
| web | ||
| lib.status | ||
| lib_analyzer.status | ||
| lib_app_jit.status | ||
| lib_dart2js.status | ||
| lib_dartdevc.status | ||
| lib_kernel.status | ||
| lib_precompiled.status | ||
| lib_vm.status | ||