-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
VMOptions directive is ignored in generated tests #483
Labels
area-test
Cross-cutting test issues (use area- labels for specific failures; not used for package:test).
Comments
Set owner to @peter-ahe-google. |
Why was this assigned to me? Set owner to @sgmitrovic. |
cc @kasperl. |
Assigned to Peter who authored the generated tests. Added Accepted label. |
Set owner to @kasperl. |
Set owner to @sgjesse. |
Fixed in http://codereview.chromium.org/8679025/. Added Fixed label. |
crelier
added
Type-Defect
area-test
Cross-cutting test issues (use area- labels for specific failures; not used for package:test).
labels
Nov 24, 2011
This was referenced Oct 29, 2020
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-test
Cross-cutting test issues (use area- labels for specific failures; not used for package:test).
If the line
// VMOptions=--enable_type_checks
appears in a template test such as language/TypeVariableBoundsTest,
it gets copied to the generated tests (this is fine). However, the generated tests are not invoked with the expected --enable_type_checks flag.
The text was updated successfully, but these errors were encountered: