I've been looking at the yaml files in the tmt distribution. I'm a
tmt newbie, so don't laugh at me. :-)
On Tue, Jan 10, 2023 at 12:47 AM Petr Pisar <ppisar@xxxxxxxxxx> wrote:
> [32m[17:03:30] [+] [worker_0] [stdout] [Fedora-Rawhide:x86_64:/plans/ci] Found 1 plan. [0m
> [32m[17:03:30] [+] [worker_0] [stdout] [Fedora-Rawhide:x86_64:/plans/ci] [0m
> [32m[17:03:30] [+] [worker_0] [stdout] [Fedora-Rawhide:x86_64:/plans/ci] /plans/ci [0m
> [32m[17:03:30] [+] [worker_0] [stdout] [Fedora-Rawhide:x86_64:/plans/ci] summary: CI Gating Plan [0m
> [33m[17:03:30] [W] [worker_0] [stderr] [Fedora-Rawhide:x86_64:/plans/ci] warn: /plans/ci:discover - {'how': 'fmf', 'directory': 'tests'} is not valid under any of the given schemas [0m
> [33m[17:03:30] [W] [worker_0] [stderr] [Fedora-Rawhide:x86_64:/plans/ci] warn: /plans/ci:execute - {'how': 'beakerlib'} is not valid under any of the given schemas [0m
> [33m[17:03:30] [W] [worker_0] [stderr] [Fedora-Rawhide:x86_64:/plans/ci] Unsupported execute method 'beakerlib' in the '/plans/ci' plan. [0m
It looks like this is correct. First, there is no "directory" in
%{python3_sitelib}/tmt/schemas/discover/fmf.yaml. There is a "path",
but I don't think it is needed since tmt reports that it can find the
test without that directive.
Second, there is no beakerlib.yaml in
%{python3_sitelib}/tmt/schemas/execute. The examples all use "tmt" as
the execute method. That seems right, since the test itself specifies
"framework: beakerlib".
I made both changes, and ran:
tmt run --all provision --how local report --how display
which produced this output:
/var/tmp/tmt/run-001
/plans/ci
discover
how: fmf
directory: /home/jamesjer/Projects/fedora/libmpc
summary: 1 test selected
provision
how: local
distro: Fedora Linux 37 (Workstation Edition)
summary: 1 guest provisioned
prepare
how: install
summary: Install required packages
name: requires
package: beakerlib
how: install
summary: Install recommended packages
name: recommends
package: texinfo, yum-utils, mpfr-devel and 5 more
summary: 2 preparations applied
execute
how: tmt
summary: 1 test executed
report
how: display
summary: 1 warn
finish
summary: 0 tasks completed
total: 1 warn
I found log.txt in /var/tmp/tmt/run-001 and searched for the warning:
00:16:06 out:
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
00:16:06 out: :: Setup
00:16:06 out:
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
00:16:06 out:
00:16:06 out: :: [ 17:16:00 ] :: [ PASS ] ::
Creating tmp directory (Expected 0, got 0)
00:16:06 out: :: [ 17:16:00 ] :: [ PASS ] ::
Command 'pushd /tmp/tmp.rKSvX9MnOj' (Expected 0, got 0)
00:16:06 out: :: [ 17:16:00 ] :: [ LOG ] ::
rlFetchSrcForInstalled: Fetching source rpm for installed
libmpc-1.2.1-5.fc37
00:16:06 out: :: [ 17:16:00 ] :: [ LOG ] ::
trying download from
'https://kojipkgs.fedoraproject.org/packages/libmpc/1.2.1/5.fc37/src/libmpc-1.2.1-5.fc37.src.rpm'
00:16:06 out: :: [ 17:16:00 ] :: [ PASS ] ::
Checking for the presence of libmpc rpm
00:16:06 out: :: [ 17:16:00 ] :: [ LOG ] ::
Package versions:
00:16:06 out: :: [ 17:16:00 ] :: [ LOG ] ::
libmpc-1.2.1-5.fc37.x86_64
00:16:06 out: :: [ 17:16:01 ] :: [ FAIL ] ::
Command 'dnf builddep -y libmpc' (Expected 0, got 1)
00:16:06 out: :: [ 17:16:01 ] :: [ PASS ] ::
Command 'rpm --define='_topdir /tmp/tmp.rKSvX9MnOj' -Uvh *src.rpm'
(Expected 0, got 0)
00:16:06 out: :: [ 17:16:05 ] :: [ PASS ] ::
Command 'rpmbuild --define='_topdir /tmp/tmp.rKSvX9MnOj' -bc
SPECS/libmpc.spec' (Expected 0, got 0)
00:16:06 out:
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
00:16:06 out: :: Duration: 5s
00:16:06 out: :: Assertions: 5 good, 1 bad
00:16:06 out: :: RESULT: WARN (Setup)
I guess that's because I ran tmt on my local machine as a regular
user, rather than using the recommended method of running in a VM,
right? I'm going to commit those changes and rerun the tests. I
would rather see them pass than waive them.
--
Jerry James
http://www.jamezone.org/
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
