action #46967
closed
[functional][u][tools] warning in bootloader_zkvm: Calling Net::SSH2::Channel::readline in non-blocking mode is usually a programming error
Added by mgriessmeier almost 6 years ago.
Updated almost 5 years ago.
Category:
Regressions/Crashes
Description
Observation¶
openQA test in scenario OpenQA::Schema::Result::TestSuites=HASH(0xaeb1b28) fails in
bootloader_zkvm
[2019-02-01T10:03:04.876 CET] [debug] Connection to root@s390p8.suse.de established
Calling Net::SSH2::Channel::readline in non-blocking mode is usually a programming error at /usr/lib/os-autoinst/backend/baseclass.pm line 1221.
First time seeing this in Beta2 Candidate of SLE15-SP1, restarting worked though
Workaround¶
Reproducible¶
Fails since (at least) Build 158.4 (current job)
Expected result¶
Last good: 157.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
UPDATE¶
bootloader_zkvm failures are not related to this warning. This warning comes from perl-Net-SSH2 version 0.66 (commit ad5f9f0 ("Warn about readline being called in non-blocking mode"). I guess 157.1 (last good) also had this warning, just didn't fail due some other reason. I'll fix this issue during fixing #45863.
- Description updated (diff)
actually this also occurs in tests which are successful, so it's more a warning
It's possible to debug it if you set debug mode for SSH2: Net::SSH2->new(debug => 1);
Beware it takes a lot data.
- Subject changed from [functional][tools] test fails in bootloader_zkvm: Calling Net::SSH2::Channel::readline in non-blocking mode is usually a programming error to [functional][u][tools] test fails in bootloader_zkvm: Calling Net::SSH2::Channel::readline in non-blocking mode is usually a programming error
- Target version set to future
@mgriessmeier please always use a team-assignment like [u] or [y]. As you know, we want the teams to be more independant so we should rely less on "catch-all" approaches like people like me to crosscheck the tickets that fall between the silos ;)
- Related to action #46919: [functional][u][svirt][sporadic] auto_review:"IO::Socket::INET: connect: Connection timed out" added
@mgriessmeier: can you please change the version of this ticket to "Planned Kernel&Network"?
- Target version changed from future to 454
- Assignee set to pvorel
- Target version changed from 454 to 445
- Parent task set to #45863
Actually, this must be solved during fixing svirt serial implementation in #45863.
- Subject changed from [functional][u][tools] test fails in bootloader_zkvm: Calling Net::SSH2::Channel::readline in non-blocking mode is usually a programming error to [functional][u][tools] warning in bootloader_zkvm: Calling Net::SSH2::Channel::readline in non-blocking mode is usually a programming error
- Description updated (diff)
- Description updated (diff)
- Parent task deleted (
#45863)
- Related to action #45863: [s390x][svirt][ltp] Fix serial terminal console implementation for svirt backend and use it's output added
- Target version changed from 445 to 454
- Related to action #49394: [s390x][svirt] Print content of kernel log and serial console into "Serial output" field added
- Target version changed from 454 to future
- Assignee deleted (
pvorel)
- Category changed from 132 to Feature requests
- Priority changed from Normal to High
- Category changed from Feature requests to Regressions/Crashes
- Status changed from New to Resolved
- Assignee set to mkittler
- Target version changed from future to Done
Also available in: Atom
PDF