autoqa-devel June 2011

autoqa-devel@lists.fedorahosted.org

12 participants
97 discussions

[AutoQA] #224: initscripts: installing older package then current fails
by fedora-badges 10 Oct '11

10 Oct '11

#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_ssh_… 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/openssh-… 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

1 2

[AutoQA] #282: Update minimum python version requirement to 2.6
by fedora-badges 17 Aug '11

17 Aug '11

#282: Update minimum python version requirement to 2.6 --------------------+------------------------------------------------------- Reporter: jlaska | Owner: Type: task | Status: new Priority: major | Milestone: 0.5.0 Component: core | Keywords: --------------------+------------------------------------------------------- Supporting RHEL-5 (python-2.4) isn't fun. The packaging and python support is so dramatically different. I'd like to upgrade our autoqa/autotest server to use RHEL-6. I'd consider using a stable Fedora release, but as tflink pointed out, I'm even less excited about updating our infrastructure every 6 months. This ticket is intended to track: 1. Removal of the epel-5 packages and repositories 2. Any code updates/simplification (e.g. use of finally) -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/282> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 6

[AutoQA] #313: ResultsDB: Script to parse the mailing-list and fill the resultsDB
by fedora-badges 10 Aug '11

10 Aug '11

#313: ResultsDB: Script to parse the mailing-list and fill the resultsDB ----------------------+----------------------------------------------------- Reporter: vhumpa | Owner: vhumpa Type: task | Status: new Priority: major | Milestone: Resultdb Component: resultdb | Keywords: ----------------------+----------------------------------------------------- To continue development and AutoQA/ResultDB integration we need to have ResultsDB filled with relevant data for testing. Later on we might need to put already existing result data into ResultDB when it becomes operational. All the past data sits in the mailing list archives, so let's create a script that will parse the stored mbox file and input the data into ResultDB using it's input API. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/313> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 6

[AutoQA] #330: upgradepath: improve behavior when pushing update to multiple releases
by fedora-badges 04 Aug '11

04 Aug '11

#330: upgradepath: improve behavior when pushing update to multiple releases -------------------------+-------------------------------------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: major | Milestone: 0.5.0 Component: tests | Keywords: -------------------------+-------------------------------------------------- This ticket stems from my talk to mcepl and our following discussion: https://fedorahosted.org/pipermail/autoqa-devel/2011-May/002215.html Package maintainers usually push fixes to many Fedora releases at once. Upgradepath usually fails for all but the highest one. We should improve the output. 1. If upgradepath passes, no changes. 2. If upgradepath fails, check update-pending repos for the failed sections and determine whether the same proposed update is available there. If it is, check upgradepath again and determine whether test would pass if all those proposed updates for all releases were pushed at the same time. Inform the user about it. 3. If the condition in 2) is valid, change FAIL result to NEEDS_INSPECTION. I'll gladly take this ticket when I finish my current work. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/330> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 14

[AutoQA] #102: post-iso-build hook
by fedora-badges 03 Aug '11

03 Aug '11

#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

1 3

[AutoQA] #209: complete auto CD install test driver
by fedora-badges 02 Aug '11

02 Aug '11

#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

1 2

[AutoQA] #149: rpmlint: Provide whitelisting of messages
by fedora-badges 28 Jul '11

28 Jul '11

#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

1 2

[AutoQA] #104: virtguest.py: accept iso image(s) as install location
by fedora-badges 21 Jul '11

21 Jul '11

#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

1 3

[AutoQA] #308: depcheck: Handle packages with "Conflicts:" declarations better than just failing them
by fedora-badges 18 Jul '11

18 Jul '11

#308: depcheck: Handle packages with "Conflicts:" declarations better than just failing them -------------------------+-------------------------------------------------- Reporter: tflink | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Package Update Acceptance Test Plan Component: core | Keywords: -------------------------+-------------------------------------------------- In a recent [http://autoqa.fedoraproject.org/results/82955-autotest/qa03.c.fedoraproject… test for mediawiki on f13], depcheck rejected the updated because it conflicted with pho-common. The package conflicts with php-common because of a "Conflicts: php-common = 5.3.1" in the spec file for mediawiki starting with 1.16.2-56 ([http://pkgs.fedoraproject.org/gitweb/?p=mediawiki.git;a=blob;f=mediawiki.sp… current spec file]) I can't imagine that this is the only package with a "Conflicts:" declaration and I don't think that we should be just failing packages like that. Maybe the "Conflicts:" should be checked somewhere, I'm just thinking that it should be somewhere other than depcheck. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/308> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #248: depcheck: simultaneous run may report incorrect results
by fedora-badges 18 Jul '11

18 Jul '11

#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

1 9

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel June 2011