You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A few of the isolate tests are using the unittest package along with a custom configuration for it used just by those tests. The unittest package was deprecated years ago, well before Dart 2.0. It has not been touched or maintained in ages. These isolate tests are using it:
They use this helper library which also uses unittest:
tests/lib_2/isolate/remote_unittest_helper.dart
I spent some time trying to migrate these myself, but I don't understand the isolate API well enough to do so. There is no plan to migrate unittest to null safety, which means until these tests are migrated off unittest, there will be no way to migrate these tests to null safety and thus no way to test the corresponding isolate API from null safe code.
The text was updated successfully, but these errors were encountered:
munificent
added
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
NNBD
Issues related to NNBD Release
labels
Feb 26, 2020
A few of the isolate tests are using the unittest package along with a custom configuration for it used just by those tests. The unittest package was deprecated years ago, well before Dart 2.0. It has not been touched or maintained in ages. These isolate tests are using it:
They use this helper library which also uses unittest:
I spent some time trying to migrate these myself, but I don't understand the isolate API well enough to do so. There is no plan to migrate unittest to null safety, which means until these tests are migrated off unittest, there will be no way to migrate these tests to null safety and thus no way to test the corresponding isolate API from null safe code.
The text was updated successfully, but these errors were encountered: