[AutoQA] #125: initscripts: Choosing the right repo for dependencies
by fedora-badges
#125: initscripts: Choosing the right repo for dependencies
-------------------------+--------------------------------------------------
Reporter: kparal | Owner: jskladan
Type: task | Status: new
Priority: major | Milestone:
Component: tests | Version: 1.0
Keywords: initscripts |
-------------------------+--------------------------------------------------
Currently after new Koji build the initscripts test downloads all relevant
binary packages (related to the particular source package) and installs
them. But the RPM dependencies are installed from stable/updates repos,
not from Koji. Also the dependencies parsed out of Makefile are installed
from stable/updates repos.
We have to inquire a little more into this situation. Is it
sufficient/desirable? Or is it desirable to download dependencies from
updates-testing or bleeding edge Koji? May the initscripts test sometimes
fail because of insufficient dependencies are in stable/updates repos?
This also depends on cases when we are going to use initscripts test. If
it will be used with Bodhi hook, it will be probably easier to solve it
than when used with Koji hook.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/125>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 6 months
[AutoQA] #224: initscripts: installing older package then current fails
by fedora-badges
#224: initscripts: installing older package then current fails
--------------------+-------------------------------------------------------
Reporter: kparal | Owner: jskladan
Type: defect | Status: new
Priority: major | Milestone: Package Update Acceptance Test Plan
Component: tests | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
In initscripts test we install some packages. But if those packages are
older than currently installed, the test crashes. Usually we test only
very new package builds, but in same cases this can also happen and we
should have it handled.
{{{
[root@aqd autoqa]# autoqa post-koji-build --kojitag dist-f13
openssh-5.4p1-1.fc13 --local -t initscripts
14:28:27 INFO | Writing results to /usr/share/autotest/client/results
/post-koji-build:initscripts.noarch
14:28:27 INFO | Initializing the state engine
14:28:27 DEBUG| Persistent state variable __steps now set to []
14:28:27 INFO | Symlinking init scripts
14:28:27 DEBUG| Running 'grep :initdefault: /etc/inittab'
14:28:27 DEBUG| Running 'ln -sf /usr/share/autotest/client/tools/autotest
/etc/init.d/autotest'
14:28:27 DEBUG| Running 'ln -sf /usr/share/autotest/client/tools/autotest
/etc/rc3.d/S99autotest'
14:28:27 DEBUG| Dropping caches
14:28:27 DEBUG| Running 'sync'
14:28:27 DEBUG| Running 'echo 3 > /proc/sys/vm/drop_caches'
14:28:27 DEBUG| Running 'rpm -qa'
14:28:28 INFO | START ---- ---- timestamp=1284121708
localtime=Sep 10 14:28:28
14:28:28 DEBUG| Persistent state variable __group_level now set to 1
14:28:28 INFO | START initscripts initscripts
timestamp=1284121708 localtime=Sep 10 14:28:28
14:28:28 DEBUG| Persistent state variable __group_level now set to 2
14:28:28 DEBUG| Crash handling system enabled
14:28:28 DEBUG| Running 'rpm -qa'
14:28:29 INFO |
/etc/yum.repos.d/beakerlib.repo:baseurl=http://afri.fedorapeople.org/beakerlib/
14:28:29 DEBUG| Running 'yum -y install beakerlib'
14:28:29 DEBUG| [stdout] Setting up Install Process
14:28:30 DEBUG| [stdout] Package beakerlib-1.3-1.fc13.noarch already
installed and latest version
14:28:30 DEBUG| [stdout] Nothing to do
14:28:31 INFO | Test started. Number of iterations: 1
14:28:31 INFO | Executing iteration 1 of 1
14:28:31 INFO | Dropping caches between iterations
14:28:31 DEBUG| Running 'sync'
14:28:31 DEBUG| Running 'echo 3 > /proc/sys/vm/drop_caches'
14:28:31 INFO | ========================================
14:28:31 INFO | openssh-5.4p1-1.fc13
14:28:31 INFO | ========================================
14:28:32 INFO | Saving RPMs to
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms
14:28:32 INFO | Grabbing
http://koji.fedoraproject.org/packages/openssh/5.4p1/1.fc13/x86_64/pam_ss...
14:28:34 INFO | Grabbing
http://koji.fedoraproject.org/packages/openssh/5.4p1/1.fc13/x86_64
/openssh-askpass-5.4p1-1.fc13.x86_64.rpm
14:28:35 INFO | Grabbing
http://koji.fedoraproject.org/packages/openssh/5.4p1/1.fc13/x86_64
/openssh-server-5.4p1-1.fc13.x86_64.rpm
14:28:37 INFO | Grabbing
http://koji.fedoraproject.org/packages/openssh/5.4p1/1.fc13/x86_64
/openssh-clients-5.4p1-1.fc13.x86_64.rpm
14:28:39 INFO | Grabbing
http://koji.fedoraproject.org/packages/openssh/5.4p1/1.fc13/x86_64/openss...
14:28:41 DEBUG| Running 'yum -y --nogpgcheck localinstall
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/pam_ssh_agent_auth-0.9.2-24.1.fc13.x86_64.rpm
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-
askpass-5.4p1-1.fc13.x86_64.rpm
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-
server-5.4p1-1.fc13.x86_64.rpm
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-
clients-5.4p1-1.fc13.x86_64.rpm
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-5.4p1-1.fc13.x86_64.rpm'
14:28:47 ERROR| Exception escaping from test:
Traceback (most recent call last):
File "/usr/share/autotest/client/common_lib/test.py", line 384, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/usr/share/autotest/client/common_lib/test.py", line 570, in
_call_test_function
return func(*args, **dargs)
File "/usr/share/autotest/client/common_lib/test.py", line 279, in
execute
postprocess_profiled_run, args, dargs)
File "/usr/share/autotest/client/common_lib/test.py", line 201, in
_call_run_once
self.run_once(*args, **dargs)
File "/usr/lib/python2.6/site-packages/autoqa/decorators.py", line 71,
in newf
f_result = f(*args, **kwargs) #call the decorated function
File "/usr/share/autotest/client/site_tests/initscripts/initscripts.py",
line 158, in run_once
utils.system_output(cmd)
File "/usr/share/autotest/client/common_lib/utils.py", line 689, in
system_output
args=args).stdout
File "/usr/share/autotest/client/common_lib/utils.py", line 425, in run
"Command returned non-zero exit status")
CmdError: Command <yum -y --nogpgcheck localinstall
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/pam_ssh_agent_auth-0.9.2-24.1.fc13.x86_64.rpm
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-
askpass-5.4p1-1.fc13.x86_64.rpm
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-
server-5.4p1-1.fc13.x86_64.rpm
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-
clients-5.4p1-1.fc13.x86_64.rpm
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-5.4p1-1.fc13.x86_64.rpm>
failed, rc=1, Command returned non-zero exit status
* Command:
yum -y --nogpgcheck localinstall
/usr/share/autotest/client/tmp/tmpS_K1om
_initscripts/rpms/pam_ssh_agent_auth-0.9.2-24.1.fc13.x86_64.rpm
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-
askpass-5.4p1-1.fc13.x86_64.rpm
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-
server-5.4p1-1.fc13.x86_64.rpm
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-
clients-5.4p1-1.fc13.x86_64.rpm
/usr/share/autotest/client/tmp/tmpS_K1om_i
nitscripts/rpms/openssh-5.4p1-1.fc13.x86_64.rpm
Exit status: 1
Duration: 0
stdout:
Setting up Local Package Process
Examining
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/pam_ssh_agent_auth-0.9.2-24.1.fc13.x86_64.rpm:
pam_ssh_agent_auth-0.9.2-24.1.fc13.x86_64
Marking
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/pam_ssh_agent_auth-0.9.2-24.1.fc13.x86_64.rpm
to be installed
Examining /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms
/openssh-askpass-5.4p1-1.fc13.x86_64.rpm: openssh-
askpass-5.4p1-1.fc13.x86_64
Marking /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-
askpass-5.4p1-1.fc13.x86_64.rpm to be installed
Examining /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms
/openssh-server-5.4p1-1.fc13.x86_64.rpm: openssh-
server-5.4p1-1.fc13.x86_64
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-
server-5.4p1-1.fc13.x86_64.rpm: does not update installed package.
Examining /usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms
/openssh-clients-5.4p1-1.fc13.x86_64.rpm: openssh-
clients-5.4p1-1.fc13.x86_64
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-
clients-5.4p1-1.fc13.x86_64.rpm: does not update installed package.
Examining
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-5.4p1-1.fc13.x86_64.rpm:
openssh-5.4p1-1.fc13.x86_64
/usr/share/autotest/client/tmp/tmpS_K1om_initscripts/rpms/openssh-5.4p1-1.fc13.x86_64.rpm:
does not update installed package.
Resolving Dependencies
--> Running transaction check
---> Package openssh-askpass.x86_64 0:5.4p1-1.fc13 set to be installed
--> Processing Dependency: openssh = 5.4p1-1.fc13 for package: openssh-
askpass-5.4p1-1.fc13.x86_64
--> Processing Dependency: libX11.so.6()(64bit) for package: openssh-
askpass-5.4p1-1.fc13.x86_64
--> Processing Dependency: libatk-1.0.so.0()(64bit) for package: openssh-
askpass-5.4p1-1.fc13.x86_64
--> Processing Dependency: libcairo.so.2()(64bit) for package: openssh-
askpass-5.4p1-1.fc13.x86_64
--> Processing Dependency: libfontconfig.so.1()(64bit) for package:
openssh-askpass-5.4p1-1.fc13.x86_64
--> Processing Dependency: libgdk-x11-2.0.so.0()(64bit) for package:
openssh-askpass-5.4p1-1.fc13.x86_64
--> Processing Dependency: libgdk_pixbuf-2.0.so.0()(64bit) for package:
openssh-askpass-5.4p1-1.fc13.x86_64
--> Processing Dependency: libgtk-x11-2.0.so.0()(64bit) for package:
openssh-askpass-5.4p1-1.fc13.x86_64
--> Processing Dependency: libpango-1.0.so.0()(64bit) for package:
openssh-askpass-5.4p1-1.fc13.x86_64
--> Processing Dependency: libpangocairo-1.0.so.0()(64bit) for package:
openssh-askpass-5.4p1-1.fc13.x86_64
--> Processing Dependency: libpangoft2-1.0.so.0()(64bit) for package:
openssh-askpass-5.4p1-1.fc13.x86_64
---> Package pam_ssh_agent_auth.x86_64 0:0.9.2-24.1.fc13 set to be
installed
--> Running transaction check
---> Package atk.x86_64 0:1.30.0-1.fc13 set to be installed
---> Package cairo.x86_64 0:1.8.10-1.fc13 set to be installed
--> Processing Dependency: libpng12.so.0(PNG12_0)(64bit) for package:
cairo-1.8.10-1.fc13.x86_64
--> Processing Dependency: libpixman-1.so.0()(64bit) for package:
cairo-1.8.10-1.fc13.x86_64
--> Processing Dependency: libXrender.so.1()(64bit) for package:
cairo-1.8.10-1.fc13.x86_64
--> Processing Dependency: libpng12.so.0()(64bit) for package:
cairo-1.8.10-1.fc13.x86_64
---> Package fontconfig.x86_64 0:2.8.0-1.fc13 set to be installed
---> Package gtk2.x86_64 0:2.20.1-1.fc13 set to be installed
--> Processing Dependency: libXrandr >= 1.2.99.4-2 for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: libtiff >= 3.6.1 for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: hicolor-icon-theme for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: libXrandr.so.2()(64bit) for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: libtiff.so.3()(64bit) for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: libXdamage.so.1()(64bit) for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: libXcursor.so.1()(64bit) for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: libcups.so.2()(64bit) for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: libXi.so.6()(64bit) for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: libjasper.so.1()(64bit) for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: libXext.so.6()(64bit) for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: libXcomposite.so.1()(64bit) for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: libXinerama.so.1()(64bit) for package:
gtk2-2.20.1-1.fc13.x86_64
--> Processing Dependency: libXfixes.so.3()(64bit) for package:
gtk2-2.20.1-1.fc13.x86_64
---> Package libX11.x86_64 0:1.3.1-3.fc13 set to be installed
--> Processing Dependency: libX11-common = 1.3.1-3.fc13 for package:
libX11-1.3.1-3.fc13.x86_64
--> Processing Dependency: libxcb.so.1()(64bit) for package:
libX11-1.3.1-3.fc13.x86_64
---> Package openssh-askpass.x86_64 0:5.4p1-1.fc13 set to be installed
--> Processing Dependency: openssh = 5.4p1-1.fc13 for package: openssh-
askpass-5.4p1-1.fc13.x86_64
---> Package pango.x86_64 0:1.28.0-1.fc13 set to be installed
--> Processing Dependency: libthai >= 0.1.9 for package:
pango-1.28.0-1.fc13.x86_64
--> Processing Dependency: libthai.so.0(LIBTHAI_0.1)(64bit) for package:
pango-1.28.0-1.fc13.x86_64
--> Processing Dependency: libthai.so.0()(64bit) for package:
pango-1.28.0-1.fc13.x86_64
--> Processing Dependency: libXft.so.2()(64bit) for package:
pango-1.28.0-1.fc13.x86_64
--> Running transaction check
---> Package cups-libs.x86_64 1:1.4.4-5.fc13 set to be installed
--> Processing Dependency: libgnutls.so.26(GNUTLS_1_4)(64bit) for package:
1:cups-libs-1.4.4-5.fc13.x86_64
--> Processing Dependency: libavahi-common.so.3()(64bit) for package: 1
:cups-libs-1.4.4-5.fc13.x86_64
--> Processing Dependency: libgnutls.so.26()(64bit) for package: 1:cups-
libs-1.4.4-5.fc13.x86_64
--> Processing Dependency: libavahi-client.so.3()(64bit) for package: 1
:cups-libs-1.4.4-5.fc13.x86_64
---> Package hicolor-icon-theme.noarch 0:0.12-1.fc13 set to be installed
---> Package jasper-libs.x86_64 0:1.900.1-15.fc13 set to be installed
---> Package libX11-common.noarch 0:1.3.1-3.fc13 set to be installed
---> Package libXcomposite.x86_64 0:0.4.1-2.fc13 set to be installed
---> Package libXcursor.x86_64 0:1.1.10-4.fc13 set to be installed
--> Processing Dependency: dmz-cursor-themes for package:
libXcursor-1.1.10-4.fc13.x86_64
---> Package libXdamage.x86_64 0:1.1.2-2.fc13 set to be installed
---> Package libXext.x86_64 0:1.1.2-2.fc13 set to be installed
---> Package libXfixes.x86_64 0:4.0.4-2.fc13 set to be installed
---> Package libXft.x86_64 0:2.1.14-1.fc13 set to be installed
---> Package libXi.x86_64 0:1.3.2-1.fc13 set to be installed
---> Package libXinerama.x86_64 0:1.1-2.fc13 set to be installed
---> Package libXrandr.x86_64 0:1.3.0-5.fc13 set to be installed
---> Package libXrender.x86_64 0:0.9.5-1.fc13 set to be installed
---> Package libpng.x86_64 2:1.2.44-1.fc13 set to be installed
---> Package libthai.x86_64 0:0.1.14-2.fc13 set to be installed
---> Package libtiff.x86_64 0:3.9.4-1.fc13 set to be installed
---> Package libxcb.x86_64 0:1.5-1.fc13 set to be installed
--> Processing Dependency: libXau.so.6()(64bit) for package:
libxcb-1.5-1.fc13.x86_64
---> Package openssh-askpass.x86_64 0:5.4p1-1.fc13 set to be installed
--> Processing Dependency: openssh = 5.4p1-1.fc13 for package: openssh-
askpass-5.4p1-1.fc13.x86_64
---> Package pixman.x86_64 0:0.18.0-1.fc13 set to be installed
--> Running transaction check
---> Package avahi.x86_64 0:0.6.25-7.fc13 set to be installed
--> Processing Dependency: libdaemon >= 0.11 for package:
avahi-0.6.25-7.fc13.x86_64
--> Processing Dependency: dbus for package: avahi-0.6.25-7.fc13.x86_64
--> Processing Dependency: libdaemon.so.0()(64bit) for package:
avahi-0.6.25-7.fc13.x86_64
---> Package dmz-cursor-themes.noarch 0:0.4-3.fc13 set to be installed
---> Package gnutls.x86_64 0:2.8.6-2.fc13 set to be installed
--> Processing Dependency: libtasn1.so.3(LIBTASN1_0_3)(64bit) for package:
gnutls-2.8.6-2.fc13.x86_64
--> Processing Dependency: libtasn1.so.3()(64bit) for package:
gnutls-2.8.6-2.fc13.x86_64
---> Package libXau.x86_64 0:1.0.5-1.fc12 set to be installed
---> Package openssh-askpass.x86_64 0:5.4p1-1.fc13 set to be installed
--> Processing Dependency: openssh = 5.4p1-1.fc13 for package: openssh-
askpass-5.4p1-1.fc13.x86_64
--> Running transaction check
---> Package dbus.x86_64 1:1.2.24-1.fc13 set to be installed
---> Package libdaemon.x86_64 0:0.14-1.fc13 set to be installed
---> Package libtasn1.x86_64 0:2.4-2.fc13 set to be installed
---> Package openssh-askpass.x86_64 0:5.4p1-1.fc13 set to be installed
--> Processing Dependency: openssh = 5.4p1-1.fc13 for package: openssh-
askpass-5.4p1-1.fc13.x86_64
--> Finished Dependency Resolution
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
stderr:
Error: Package: openssh-askpass-5.4p1-1.fc13.x86_64 (/openssh-
askpass-5.4p1-1.fc13.x86_64)
Requires: openssh = 5.4p1-1.fc13
Installed: openssh-5.4p1-3.fc13.x86_64 (@updates)
openssh = 5.4p1-3.fc13
Available: openssh-5.4p1-1.fc13.x86_64 (fedora)
openssh = 5.4p1-1.fc13
}}}
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/224>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 6 months
[AutoQA] #102: post-iso-build hook
by fedora-badges
#102: post-iso-build hook
----------------------+-----------------------------------------------------
Reporter: wwoods | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: watchers | Version: 1.0
Keywords: |
----------------------+-----------------------------------------------------
We need one (or more) standard locations where new iso images get posted
for testing, and a watcher that can monitor for new iso images and launch
appropriate installation/sanity tests.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/102>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 8 months
[AutoQA] #209: complete auto CD install test driver
by fedora-badges
#209: complete auto CD install test driver
-------------------+--------------------------------------------------------
Reporter: liam | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: tests | Version: 1.0
Keywords: |
-------------------+--------------------------------------------------------
complete the cd_install.py as dvd_install.py to support CD install, with
some functions like automatically swap CD when CD1 install was completed.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/209>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 8 months
[AutoQA] #149: rpmlint: Provide whitelisting of messages
by fedora-badges
#149: rpmlint: Provide whitelisting of messages
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Package update tests
Component: tests | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
We need to provide some whitelisting capability of rpmlint packages, so
the package maintainers can mark some messages as invalid. We will also
probably want to mark some messages as invalid by default for the whole
Fedora project.
As an interesting inspiration, look at lintian project (validation of deb
packages). It provides some "overrides" on a package basis, you just
create a definition file in /etc/lintian/package_name or kind of. I have
the feeling that rpmlint provides something similar, but we need to
discover it more properly.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/149>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 9 months
[AutoQA] #104: virtguest.py: accept iso image(s) as install location
by fedora-badges
#104: virtguest.py: accept iso image(s) as install location
--------------------+-------------------------------------------------------
Reporter: wwoods | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: tests | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
allow {{{VirtGuest.create()}}} to use an iso image (or images) for its
{{{location}}} arg, and automatically choose the appropriate {{{--location
URL}}} or {{{--cdrom IMAGE}}} flag.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/104>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 9 months
[AutoQA] #248: depcheck: simultaneous run may report incorrect results
by fedora-badges
#248: depcheck: simultaneous run may report incorrect results
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: 0.4.4
Component: tests | Keywords:
--------------------+-------------------------------------------------------
This is taken from:[[BR]]
https://fedorahosted.org/pipermail/autoqa-devel/2010-November/001306.html
I have imagined a situation where two updates are accepted into
the -pending tag in quick succession. Thus we can end up with two
depcheck tests running simultaneously. And the one that was started
earlier can finish up later. It could then report incorrect result.
Do you have an idea what we can we do about that? Maybe we can
somehow write down the state of the -pending tag in the time of
starting the test, and if it is different from when the test is
finished, we can just throw away the results? Just a wild idea.
Wwoods mentioned that he's working on --accepted option for depcheck, here
is short IRC excerpt, hopefully he will provide more info soon:
{{{
(05:16:13 PM) wwoods: I'm working on a mailing list post about the
"accepted" flag
(05:19:13 PM) wwoods: the short answer is this: we mark packages as
"accepted" when they pass depcheck
(05:19:48 PM) wwoods: exactly *how* we mark the package is kind of an
implementation detail - could be a koji tag or a local database of
accepted package names or whatever
(05:20:04 PM) wwoods: but since we're already planning to give +1 karma
for packages that are accepted
(05:21:02 PM) wwoods: then we can (I hope!) just check Bodhi for each
thing in -pending
(05:21:11 PM) wwoods: if it has +1, it was previously accepted
(05:21:21 PM) wwoods: err - has a +1 from autoqa / depcheck
(05:21:51 PM) wwoods: in the future we might want to query resultsdb
instead, or use a second koji tag
(05:22:39 PM) wwoods: I'll still write a (possibly longer) explanation for
the list - or maybe a blog post
}}}
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/248>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 9 months
[AutoQA] #183: Write a script and a daemon to send signals between virt machine and host
by fedora-badges
#183: Write a script and a daemon to send signals between virt machine and host
----------------------------+-----------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Virtualization
Component: infrastructure | Version: 1.0
Keywords: |
----------------------------+-----------------------------------------------
We need to exchange some signals between virt machine and a host. For
example "autotest job finished, need to revert to previous state". We need
to write simple script that will send this signal for virt machine and a
daemon that will receive this signal in the host machine and act
accordingly.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/183>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 9 months
Re: Virtualization support
by Scott M Ferguson
> Hello Scott,
>
> I'm not exactly sure I get the idea. The autotest server already
> handles starting the task and collecting results (arrows 2. and 3. in
> the picture I added to
> https://fedorahosted.org/autoqa/ticket/183#comment:description). Ticket
> #183 mainly concerns arrow 4., signaling to the host (of that autotest
> client VM). We can use it for reverting the VM to the previous state
> (I think that's the main reason we need all of this). In the Virtualization
> milestone there are other tickets that cover remaining parts of that
> picture.
>
> So, the problem of ticket #183 is not getting the results (autotest handles
> that for us), but telling the host (of that VM) "do something" right after
> completing the test.
>
> Are we on the same page? Maybe I have missed something. Tell me.
>
> Thanks,
> Kamil
>
Kamil,
We were on a different page and it's completely due to lack-of-sleep
on my end, but that's another story (4-week-old daughter). Thanks for
clarifying. All should be well now :)
Best,
Scott
12 years, 9 months
[AutoQA] #208: update minimon to transport logs between guest and host via virtio
by fedora-badges
#208: update minimon to transport logs between guest and host via virtio
-------------------+--------------------------------------------------------
Reporter: liam | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: tests | Version: 1.0
Keywords: |
-------------------+--------------------------------------------------------
Since minimon has to use network during test, some test cases will not
activate network during test,in this case, minimon can not transport logs
to host, test also be identified fail even it was successfully run.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/208>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 11 months