-
Notifications
You must be signed in to change notification settings - Fork 30.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
V8 tests failing on v12.16.0+ #32076
Comments
@mmarchini Just for context, these failures have been noticed in the V8 CI runs before, but we agreed to be okay with this because these only affect flagged, experimental features. I agree that there’s not really something we can or should do, unless somebody really wants to dig into these failures. |
I think those are also whitespace issues because of |
@mmarchini would you be open to making a backport to 12.x to fix the whitespace issues? |
If that's the same issue, yes (it'll probably be a fresh PR to v12 instead of a backport though) |
Sgtm
…On Wed, Apr 1, 2020, 5:13 PM Matheus Marchini ***@***.***> wrote:
If that's the same issue, yes (it'll probably be a fresh PR to v12 instead
of a backport though)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#32076 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADZYV2P2MMBDKKCNEHCHDLRKOVARANCNFSM4LAUL62Q>
.
|
Fixed on #32605 |
What steps will reproduce the bug?
Checkout to v12.16.0, build V8 and run tests:
How often does it reproduce? Is there a required condition?
Every time, when the test is around 40%
What is the expected behavior?
Test should succeed
What do you see instead?
Additional information
git bisect
points to 35f2892. Not sure we can fix it though. Opening the issue anyway so folks backporting V8 commits to v12 can find the error message.The text was updated successfully, but these errors were encountered: