-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix dart2js tests on travis #570
Comments
I'm probably not the relevant one for this. @jmesserly or @sigmundch, want to take a look? I haven't been closely following the changes around large 64-bit-ish integers. |
I'm not familiar with logic on these tests, but they need to be updated to run without using literals that can't be represented in JS, or split so that those large literals are only used in VM tests. FWIW - all of these large literals are used as parameters for int32x4, which are anyways truncated to 32-bit ints. |
Due to #16. This will get the build green again.
FYI, dart-archive/typed_data#17 splits tests across two Travis jobs, and the browsers tests have been disabled for now. That way we can get the build passing again. |
Due to #16. This will get the build green again.
* Skip tests known to be failing Due to #16. This will get the build green again.
* Skip tests known to be failing Due to dart-lang/typed_data#16. This will get the build green again.
https://travis-ci.org/dart-lang/typed_data/jobs/398049453
Seems there are a few constants that make dart2js sad...
The text was updated successfully, but these errors were encountered: