Actions
action #37580
closed"Use of uninitialized value $status in right bitshift (>>) at /usr/lib/os-autoinst/osutils.pm line 128." on aarch64
Start date:
2018-06-21
Due date:
% Done:
0%
Estimated time:
Description
Observation¶
openQA test in scenario sle-15-Installer-DVD-aarch64-RAID5@aarch64 fails in
start_install
with
[2018-06-20T22:11:13.0028 UTC] [debug] Formatting 'raid/3', fmt=qcow2 size=21474836480 encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16
Use of uninitialized value $status in right bitshift (>>) at /usr/lib/os-autoinst/osutils.pm line 128.
Expected result¶
No error about "Use of uninitialized value" here
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 6 years ago
- Project changed from openQA Tests to openQA Project
- Subject changed from test fails in start_install to "Use of uninitialized value $status in right bitshift (>>) at /usr/lib/os-autoinst/osutils.pm line 128." on aarch64
- Category changed from Infrastructure to Regressions/Crashes
Updated by rpalethorpe almost 6 years ago
I also experienced this on ARM, in opencmd. The $status var is set inside an event handler, so this looks like a typical race condition between the pipe closing on child termination and the signal being received by the parent process. I'm not sure why waitpid is being called in the signal handler, unless there is a very good reason for doing something inside a signal handler then it should be avoided.
Updated by EDiGiacinto almost 6 years ago
- Related to action #33514: [tools] Use of uninitialized value $status in right bitshift (>>) added
Updated by okurz over 4 years ago
- Status changed from New to Resolved
- Assignee set to EDiGiacinto
haven't seen this for long. Might have been resolved with #33514
Actions