A slightly different approach here, since the test is testing something that isn't actually required for the interpreter, so I'm adjusting the test instead to just test the variable evaluation as normal when interpreted.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
final isOptimizedOut = !isInterpreted;The detection of the interpreted mode and different test expectations look fragile.
I think the ability to correctly evaluate `data.length` is (also) a correct behavior, so the test should just accept both behaviors without checking if interpreter is used or not.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +1 |
Thanks, Alex! Have changed the test to just allow either behavior, PTAL.
The detection of the interpreted mode and different test expectations look fragile.
I think the ability to correctly evaluate `data.length` is (also) a correct behavior, so the test should just accept both behaviors without checking if interpreter is used or not.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[pkg/vm_service] Handle lack of optimized out variables in interpreter.
Test the evaluation of the variable as normal when interpreted, and
expect the appropriate RPCError when not interpreted.
TEST=pkg/vm_service/test/evaluate_optimized_out_variable_test
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |