-
Notifications
You must be signed in to change notification settings - Fork 537
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
t/op/lex.t: Failures in test #30 on multiple operating systems #17223
Labels
Comments
Reproduced on Linux with valgrind:
If you create a file from the test case you can reproduce it outside the test script, making the result easier to read:
|
tonycoz
added a commit
that referenced
this issue
Oct 28, 2019
Fixed by ffa4682, I don't see any other similar reversions in the rest of the refactor. |
This smoke test report on OpenBSD-6.6 confirms that we've gotten past the failure in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are starting to observe failures in
t/op/lex.t
in smoke-test reports generated on a variety of operating systems, including Linux and two different versions of OpenBSD.A listing of these failing smoke-test reports is here.
Based on the
git describe
values in those reports, it seems that these failures began to occur after recent extensive revisions intoke.c
were merged into blead. @arcThe test failures are intermittent but consistently occur in test #30 from that file. The relevant code in
t/op/lext.t
is:The RT cited in the description for that test is now found here: Fuzzer-detected use-after-free in Perl_yylex.
I am attaching two files which are excerpts from the
logs/smokecurrent/log*.log
files generated in two different smoke tests I have run on OpenBSD-6.4. However, when I do a regularmake test_harness
on blead on this platform,t/op/lex.t
passes. So these failures are associated with the more stressful conditions present during smoke-testing. Note that while we have observed these failures on OpenBSD (@afresh1), we are also observing them on Linux.Thank you very much.
Jim Keenan
ad1d31a5.openbsd.smoke.log.t-op-lex-t.failures.txt
bb6e2c77.openbsd.smoke.log.t-op-lex-t.failures.txt
The text was updated successfully, but these errors were encountered: