Fix e2e 'evaluate' test to use new Closure toString format #2624
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.
As of the release of Dart 3.8 on the stable branch, DDC now produces a different String (more in line with the other Dart backends) from the
toString
of closures. Rather than using JS'stoString
on the underlyingFunction
, DDC now generates a string using the Function's RTI object.This has caused the updated test to start failing in CI:
https://github.com/dart-lang/webdev/actions/runs/15255960533
Fix the test by updating the expectation string to match the new string format.