Is gating on dist-git tests working in Fedora?
by Stef Walter
Hi there,
Is the CI pipeline running on Fedora and gating? It's really hard to
find test results.
I'm looking around both in Bodhi:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-5c64b23a18
and here Pagure:
https://src.fedoraproject.org/rpms/cockpit/pull-request/3
The Cockpit Git repository has a "test-canary" test that checks whether
CI gates on test failure. Here's what you see when you run the tests in
dist-git locally:
TASK [standard-test-scripts : Check the results]
*******************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": "grep \"^FAIL\"
/var/tmp/artifacts/test.log", "delta": "0:00:00.002181", "end":
"2018-03-26 14:04:10.414274", "failed_when_result": true, "rc": 0,
"start": "2018-03-26 14:04:10.412093", "stderr": "", "stderr_lines": [],
"stdout": "FAIL ./test-canary", "stdout_lines": ["FAIL ./test-canary"]}
/tests.retry
Cheers,
Stef
6 years
Local testing & test development - Ansible & Mock
by Michal Schorm
Hi folks,
Is there any automatized way to run the tests localy in Mock?
So far I've seen 2 options:
direct invoke "# ansible-playbook tests.yml"
or runing VM from downloaded qcow2 image
Certain tests could break my system so I'd like to not running them in
somehow isolated environment.
Also, I'd use some safe way to develop such tests. Which will lead to
broken system much more likely.
--
Should I expect this idea incorporated, or should I rather prepare some VMs?
(lesser size tan 600MB each image)
--
Michal Schorm
Associate Software Engineer
Core Services - Databases Team
Red Hat
6 years, 1 month
Ouptut for beakerlib tests
by Tim Flink
There's a bug currently open for the standard test roles where there
are duplicate output lines in the logfile output when the beakerlib
role is complete.
https://pagure.io/standard-test-roles/issue/83
The summary of the issue is this: beakerlib outputs to stdout, stderr
and a logfile which do have some duplicate information between them but
none of them are identical. As a reference to what other beakerlib
environments do, Beaker seems to put all three into separate files.
What do we want to have as the primary output of the beakerlib role?
My instinct is to use the logfile as the primary output because it is
the easiest to scan, even if it is lacking details. STDOUT and STDERR
could then be combined into a second file or kept separate yet still
included in the artifacts generated.
Any thoughts on this plan or another method for getting duplicated
lines out of the log output?
Thanks,
Tim
6 years, 1 month
