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
The kernel-precomp test harness passes runtime arguments to the compiler instead of the runtime, so this test for runtime access to script arguments is failing until the harness is fixed.
rmacnak-google
added
area-test
Cross-cutting test issues (use area- labels for specific failures; not used for package:test).
and removed
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
labels
Feb 19, 2019
The fix for #35960 broke
on app_jit(k) runs, because these expect the arguments to be
passed when creating the jit snapshot. Pass dartOptions along to
computeCompilerArguments as well, so that the
AppJitCompilerConfiguration can add them in appropriately.
Change-Id: I8c7b5a3a1689943db4e6c3785ccaf8bfdb839c2d
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/97516
Reviewed-by: Stevie Strickland <sstrickl@google.com>
Commit-Queue: Stevie Strickland <sstrickl@google.com>
The kernel-precomp test harness passes runtime arguments to the compiler instead of the runtime, so this test for runtime access to script arguments is failing until the harness is fixed.
This problem started with the commit of https://dart-review.googlesource.com/c/sdk/+/93302
and has a log at
https://dart-ci.appspot.com/log/vm-kernel-precomp-linux-debug-x64/latest/standalone_2/io/arguments_test
it fails on builders:
The text was updated successfully, but these errors were encountered: