Bug 11813

Summary:

ptest- openssh cases failed

Product:

[QA/Testing] Runtime Testing

Reporter:

oscar lopez arandas <oscarx.lopez.arandas>

Component:

general

Assignee:

Armin Kuster <akuster>

Status:

RESOLVED FIXED

QA Contact:

Severity:

normal

Priority:

Medium

CC:

libertad.gonzalez.de.la.cruz, randy.macleod, richard.purdie

Version:

2.3.1

Target Milestone:

4.99

Hardware:

NUC

OS:

x86_64

Whiteboard:

OS type for building Yocto:

---

Type of Regression:

---

Verified:

Documentation change:

No (bug/feature does not impact docs)

Attachments:

Description	Flags
ptest.log	none

Description oscar lopez arandas 2017-07-19 21:25:59 UTC

Created attachment 3883 [details]
ptest.log

poky : 6bd890d9e011014cf323e61267f8b256949d44aa 
2.3.1 rc2
HW: NUC  6i5SYH 
image:
https://autobuilder.yocto.io/pub/releases/yocto-2.3.1.rc2/machines/genericx86-64/core-image-sato-sdk-ptest-genericx86-64.hddimg

test result
https://wiki.yoctoproject.org/wiki/Ptest_6bd890d9e011014cf323e61267f8b256949d44aa
 
tests were executed and The pass rate goes back the percentage, observing  1 failures on the results and 2 skiped.

================failures====================
FAIL:  connection multiplexing
SKIP:  (not supported on this platform)
SKIP: : /var/run is unsuitable as ChrootDirectory
=====================================================

full log in attachment

Comment 1 Armin Kuster 2017-12-03 16:44:25 UTC

latest in master passes: 7.6p1
run test multiplex.sh ...
test connection multiplexing: envpass
test connection multiplexing: transfer
test connection multiplexing: forward
test connection multiplexing: status 0
test connection multiplexing: status 1
test connection multiplexing: status 4
test connection multiplexing: status 5
test connection multiplexing: status 44
test connection multiplexing: cmd check
test connection multiplexing: cmd forward local (TCP)
test connection multiplexing: cmd forward remote (TCP)
test connection multiplexing: cmd forward local (UNIX)
test connection multiplexing: cmd forward remote (UNIX)
test connection multiplexing: cmd exit
test connection multiplexing: cmd stop
PASS: connection multiplexing

Comment 2 Armin Kuster 2017-12-03 23:17:07 UTC

The interesting issue here is there is a error not noted anywhere would case this testcase not to be run.

run test connect.sh ...
/usr/lib/openssh/ptest/regress/test-exec.sh: line 490: sudo: command not found
/usr/lib/openssh/ptest/regress/test-exec.sh: line 490: sudo: command not found
/usr/lib/openssh/ptest/regress/test-exec.sh: line 559: sudo: command not found
FATAL: sshd_config broken
make: *** [Makefile:198: t-exec] Error 1
make: Target 'tests' not remade because of errors.
SKIP: agent-ptrace


In /usr/lib/openssh/ptest/regress/test-exec.sh

#SUDO=sudo
SUDO="" <<-- change made to allow tests to run.

This allow latest master to run clean.

I have reproduced the failure on pyro.

test connection multiplexing: envpass
test connection multiplexing: transfer
test connection multiplexing: forward
cmp: EOF on /usr/lib/openssh/ptest/regress/copy
ssh: corrupted copy of /usr/lib/openssh/ptest/regress/data
/usr/lib/openssh/ptest/regress/multiplex.sh: line 96:  9275 Terminated              $NC -N -Ul $OBJ/unix-1.fwd < ${DATA} > /dev/null
test connection multiplexing: status 0
test connection multiplexing: status 1
test connection multiplexing: status 4
test connection multiplexing: status 5
test connection multiplexing: status 44
test connection multiplexing: cmd check
test connection multiplexing: cmd forward local (TCP)
test connection multiplexing: cmd forward remote (TCP)
test connection multiplexing: cmd forward local (UNIX)
test connection multiplexing: cmd forward remote (UNIX)
request remote forward failed
connect to remote forwarded path failed
test connection multiplexing: cmd exit
test connection multiplexing: cmd stop
FAIL:  connection multiplexing

Comment 3 Armin Kuster 2018-11-10 20:09:51 UTC

sorry for the confusion.

I ran python tests;
| RESULTS - python.PythonTest.test_python_exists - Testcase 1145: PASSED
| RESULTS - python.PythonTest.test_python_stdout - Testcase 965: PASSED
| RESULTS - python.PythonTest.test_python_testfile - Testcase 1146: PASSED

when I run ptest-runner python manually, there are some failures but I can't find where the log for would be. I can't say we are better or worse than what was run in the last sumo release. Things I hope to learn.

Comment 4 Armin Kuster 2018-11-10 21:07:27 UTC

(In reply to comment #3)
> sorry for the confusion.
> 
> I ran python tests;
> | RESULTS - python.PythonTest.test_python_exists - Testcase 1145: PASSED
> | RESULTS - python.PythonTest.test_python_stdout - Testcase 965: PASSED
> | RESULTS - python.PythonTest.test_python_testfile - Testcase 1146: PASSED
> 
> when I run ptest-runner python manually, there are some failures but I can't
> find where the log for would be. I can't say we are better or worse than
> what was run in the last sumo release. Things I hope to learn.

sorry. got myself confused on which package this was regarding.

I am looking at openssh now

Comment 5 Armin Kuster 2018-11-10 21:58:35 UTC

sumo openssh passed now.

Comment 6 Richard Purdie 2019-06-08 15:06:52 UTC

openssh ptest issues have been resolved in master