-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Interesting TestStringsToAutomaton failure #12451
Comments
I've reproduced this and narrowed it down to the following: The built automaton is correct up to the point when the (randomly generated) term |
I've tracked it down to this exact sequence being added: You can reproduce this by adding the following code immediately after line 127 in
|
I'll also mention that:
|
This looks like a bug in the |
Thanks a lot for the detailed investigation @gsmiller. |
@jpountz of course. It's an interesting issue. I'll post a small PR shortly to work around it in this test case to avoid the periodic failures shortly. |
PR that works around the underlying bug, making sure we don't hit this sporadic test case failures until the bug eventually is fixed: #12461 |
Description
This test fails because the final automaton reports that it contains
{ 0xf0, 0x80, 0x80, 0x80 }
even though it has not been added to the automaton builder.Gradle command to reproduce
The text was updated successfully, but these errors were encountered: