The log from tmt seems correct:
http://artifacts.dev.testing-farm.io/fa33fbe9-a850-4450-a676-f3e24bfbae4f/work-shell5uNTfu/plans/shell/execute/logs/tests/login/out.log

This is a problem with non-printable unicode characters when we want to take the whole log and inject it into the Jenkins xunit file. So it's a problem with processing on my end.

Checking...

@mruprich seems the same issue you hit ....

@mvadkert yeah, this is exactly as my issue. Unfortunately I am not aware of any unicode characters in the output of the test :/

@mruprich There are some gibberish characters in the output:

http://artifacts.dev.testing-farm.io/aa19e9af-213b-4031-9cdf-e83b3bcfbb9d/work-test1JAOV_/ci/test/execute/logs/Regression/bz1715423-tcpdump-pre-creates-user-and-groups/out.log

type=CRYPTO_SESSION msg=audit(1604042479.462:861): pid=8244 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=start direction=from-server cipher=aes256-gcm@openssh.com ksize=256 mac=<implicit> pfs=curve25519-sha256 spid=8245 suid=74 rport=58310 laddr=172.31.31.0 lport=22  exe="/usr/sbin/sshd" hostname=? addr=172.31.31.161 terminal=? res=success'UID="root" AUID="unset" 

See the res=success'UID="root" part (it seems like Pagure replaces such characters with a question mark).

Not sure where it is coming from, but it is fine. I will just strip away such characters and keep only CR-LF. No need to fix anything on your side.

The same problem is in the log that Petr posted:

tcpdump logs seem fine now (with the fix): https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pipeline/job/tmt/7185/testReport/(root)/tests/

The same for zsh: https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pipeline/job/master/1524/testReport/(root)/tests/

I think we are done here. Thanks for the bug report folks ;)

@msrb works like a charm, thx :)