-
Notifications
You must be signed in to change notification settings - Fork 553
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
DragonflyBSD: t/op/magic.t has test failures since v5.35.9 #19894
Comments
|
The log provides more information: I don't see any changes in S_set_dollarzero() over that period. The calling code to that was changed in 2d3b356 but that looks fairly safe for the test that's failing. |
@cjg-cguevara, can you give this branch a spin on your DragonflyBSD smoker? Thanks. |
|
Looks like it's failing on -Duseshrplib builds. |
I don't see that in smoke-test results. (In fact, I don't yet see any results for this smoke-me branch. Where are you seeing that? |
Correction: I don't yet see any results for this branch run on Dragonfly BSD. |
|
I'm looking at the github CI results, eg. https://github.com/Perl/perl5/runs/7083910270?check_suite_focus=true |
@tonycoz, I think we have a bigger problem here. I'm getting problems with Configure without On FreeBSD-12: I know very little about |
|
So, having just now read Once I precede configuration with I note in passing, however, that Tony's branch does get How should we proceed? |
|
For your |
|
Note that my change isn't a fix - it's a workaround, I expect it will be better to TODO these tests on DragonflyBSD. I've reproduced this from straight C code, and opened https://bugs.dragonflybsd.org/issues/3319 I'll work on a better patch, probably skipping the Unicode $0 tests on DragonflyBSD |
|
On 6/29/22 21:12, Tony Cook wrote:
Note that my change isn't a /fix/ - it's a workaround, I expect it will
be better to TODO these tests on DragonflyBSD.
I've reproduced this from straight C code, and opened
https://bugs.dragonflybsd.org/issues/3319
<https://bugs.dragonflybsd.org/issues/3319>
I'll work on a better patch, probably skipping the Unicode $0 tests on
DragonflyBSD
Thanks. What I had hoped to do today -- and might get to tomorrow --
was to create a smoke-me branch that reduced t/op/magic.t to just the
two failing unit tests. I hope that would enable us to see why they
were failing as of the commit you previously cited and only on this one
platform.
|
|
Changing It seems to be all the calls to setproctitle() that cause the problem, commenting out any of the active setproctitle() calls in the C reproducer in the upstream bug stops the change in behaviour. |
The sequence of calls to setproctitle() seems to mess up some internal OS state, which ends up making the more fundamental $0 tests fail later in the file. Reported upstream as https://bugs.dragonflybsd.org/issues/3319 Fixes #19894
The sequence of calls to setproctitle() seems to mess up some internal OS state, which ends up making the more fundamental $0 tests fail later in the file. Reported upstream as https://bugs.dragonflybsd.org/issues/3319 Fixes Perl#19894
Somewhere between
v5.35.8-29-g4ccd1515c8andv5.35.9-114-gc3c9d6b15f-- approximately February 2022 -- two tests (202-203) int/op/magic.tbegan to fail in blead in DragonflyBSD -- and they continue to fail to this day.See these smoke-test reports:
PASS https://perl5.test-smoke.org/report/5015286
FAIL https://perl5.test-smoke.org/report/5016701
We only have one person submitting smoke-test reports on this OS; @cjg-cguevara, can you supply more data?
I don't have access to DragonflyBSD, so if anyone can investigate, please do so.
The text was updated successfully, but these errors were encountered: