Automatically extend the Dartium expiration date for test/coverage tasks #266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Dartium has hit its built-in expiration date, and cannot run Dart code properly unless the date is overridden using the
DARTIUM_EXPIRATION_TIME
environment variable.dart-lang/sdk#33580
This causes tests and coverage to timeout inexplicably when running content-shell, and only with a popup warning when running in Dartium.
Solution
Automatically set this flag in relevant processes launched by dart_dev to work around this issue and prevent frustrating content-shell failures.
Testing:
ddev test
/ddev coverage
in a terminal whereDARTIUM_EXPIRATION_TIME
is unset, and verify that tests pass