autoqa-devel July 2012

autoqa-devel@lists.fedorahosted.org

6 participants
17 discussions

[AutoQA] #417: Prune old autotest results [waiting upstream]
by fedora-badges 26 Sep '12

26 Sep '12

#417: Prune old autotest results [waiting upstream] -------------------------+--------------------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: major | Milestone: Packaging, Review, & Deployment Component: production | Keywords: Blocked By: | Blocking: -------------------------+--------------------------------------------- Since we execute a large number of jobs, the database fills pretty quickly and the autotest interface gets slower and slower. Lucas implemented a new script to prune the database, but we have to wait until it is released in a new autotest-server version (probably 0.14). https://github.com/autotest/autotest/issues/98 -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/417> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #251: Move autotest applications into /usr/*bin
by fedora-badges 26 Sep '12

26 Sep '12

#251: Move autotest applications into /usr/*bin -----------------------+---------------------------------------------------- Reporter: jlaska | Owner: Type: task | Status: new Priority: minor | Milestone: Packaging, Review, & Deployment Component: packaging | Keywords: -----------------------+---------------------------------------------------- The autotest package should supply binaries in /usr/bin/ ... so we can rely on PATH and not have to call autotest with the full-path (/usr/share/autotest/client/bin/autotest) when scheduling jobs in '/usr/bin/autoqa'. Alternatively, the autotest package could drop a script that updates PATH appropriately into /etc/profile.d/autotest. But yuck. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/251> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 2

[AutoQA] #419: Adjust code to Autotest API changes
by fedora-badges 26 Sep '12

26 Sep '12

#419: Adjust code to Autotest API changes -----------------------+-------------------------- Reporter: mkrizek | Owner: mkrizek Type: task | Status: new Priority: major | Milestone: Future tasks Component: autotest | Keywords: Blocked By: | Blocking: -----------------------+-------------------------- With recent proposed changes to Autotest API [1], the job here is to make appropriate adjustments to AutoQA code and make sure that everything works after that. [1] http://test.kernel.org/pipermail/autotest/2012-April/010235.html -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/419> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

[AutoQA] #191: Submit autotest for Fedora package approval
by fedora-badges 26 Sep '12

26 Sep '12

#191: Submit autotest for Fedora package approval -----------------------+---------------------------------------------------- Reporter: jlaska | Owner: Type: task | Status: new Priority: major | Milestone: Packaging and Review Component: packaging | Version: 1.0 Keywords: | -----------------------+---------------------------------------------------- * https://bugzilla.redhat.com/show_bug.cgi?id=548522 Currently stalled, pending packaging of the gwt package. This includes packaging all bundled .jar files included with gwt. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/191> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

rats_install and rats_sanity need a new maintainer
by Kamil Paral 14 Aug '12

14 Aug '12

Hongqing used to maintain rats_install and rats_sanity tests. Because he has left, we need to find a new maintainer or remove the tests. - rats_sanity has some minor scheduling issues, I'm working on it just now. Apart from that it shouldn't be a problematic test. - rats_install is currently broken, and we can start fixing it only after anaconda releases some new compose (with serial console install included). This is a problematic test and will probably require lots of maintenance (according to anaconda changes throughout the Branched period). Tao, do you feel like taking Hongqing's former responsibilities? Is there any other volunteer?

1 2

[AutoQA] #414: rats_install: run twice, once for updates, once for updates+updates-testing
by fedora-badges 14 Aug '12

14 Aug '12

#414: rats_install: run twice, once for updates, once for updates+updates-testing --------------------------+------------------------------- Reporter: kparal | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Nice to have soon Component: tests | Keywords: Blocked By: | Blocking: --------------------------+------------------------------- We decided it would be beneficial to run rats_install twice. Once for stable updates only, once for main+updates, once for main+updates+updates- testing. Currently we're running just the second option. The discussion is here: https://fedoraproject.org/wiki/QA/Meetings/20120319#t15:55:42 Change rats_install to execute twice and report both variants. The easiest way is probably to modify 'control' file to execute the job twice and modify some input argument to distinguish the two cases. Also we need to change the summary accordingly so that we can easily distinguish that in our ResultsDB view. Marking "Nice to have soon" if we can do it before F17 Final, otherwise it'll probably go into "Future tasks". -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/414> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 10

[AutoQA] #427: Purge unneeded files in autotest results dir
by fedora-badges 09 Aug '12

09 Aug '12

#427: Purge unneeded files in autotest results dir -------------------------+------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: minor | Milestone: Finger Food Component: production | Keywords: Blocked By: | Blocking: -------------------------+------------------------- Currently we have a script that periodically traverses through autotest results dir and compresses too large files. Also we use tmpwatch to remove too old results. But we still sometimes have problems with disk space and number of inodes on our servers. Autotest stores large number of files in each result directory. By cleaning those we don't want we can save resources, speed up execution of maintenance scripts and potential debugging (like grepping through results). Let's create a script that would traverse the results directory periodically and remove unneeded files. It would also compress large files, so it would call or merge the existing script. If we look into an example results dir: http://autoqa-stg.fedoraproject.org/results/100310-autotest/qa07.qa/ I believe we need to keep: {{{ /control /debug/*.DEBUG /host_keyvals /keyval /rpmguard/debug/*.DEBUG ("rpmguard" is a dynamic test name here) /rpmguard/keyval /rpmguard/results /rpmguard/status /status.log /sysinfo/installed_packages /sysinfo/uname }}} The rest of it can be deleted. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/427> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 8

[AutoQA] #157: conflicts: requested arch not respected
by fedora-badges 06 Aug '12

06 Aug '12

#157: conflicts: requested arch not respected --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: defect | Status: new Priority: major | Milestone: Component: tests | Version: 1.0 Keywords: | --------------------+------------------------------------------------------- This is a bug in the potential_conflict.py script in tests/conflicts/. Usage suggests using --arch options for specifying requested architecture to be tested. But if you look at the attached log, the first and second output match (that's correct), but the third doesn't match, even though it should. Everything was tested on x86_64 machine. Also from the usage line it is not clear whether --arch is related only to particular yum repository selection (replacing $basearch keyword), or whether it also relates to packages built for one architecture but being in different repo (e.g. i686 packages are very often in x86_64 repo). I have looked into the source code of the script and it seems that the --arch option is not used at all, just printed out in the usage help?? Seth, you're listed as script author. Any comments on that? Thanks. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/157> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 7

[AutoQA] #424: Add F17 machines and update F15 machines
by fedora-badges 02 Aug '12

02 Aug '12

#424: Add F17 machines and update F15 machines -------------------------+------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: major | Milestone: Nice to have soon Component: production | Keywords: Blocked By: | Blocking: -------------------------+------------------------------- F15 will be EOL soon. We need to upgrade those test clients. Also we have none F17 test machines ATM. We need to have some of them. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/424> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 3

[AutoQA] #421: depcheck: KeyError: 'strong_requires'
by fedora-badges 02 Aug '12

02 Aug '12

#421: depcheck: KeyError: 'strong_requires' -----------------------+------------------------ Reporter: kparal | Owner: Type: defect | Status: new Priority: critical | Milestone: Hot issues Component: tests | Keywords: Blocked By: | Blocking: -----------------------+------------------------ Since I updated our staging machines, a lot of these depcheck crashes appeared: {{{ Traceback (most recent call last): File "./depcheck", line 112, in <module> profile=opts.profile) File "/usr/share/autotest/tests/depcheck/depcheck_lib.py", line 394, in depcheck_main test_dir=temp_dir, accepted_dir=acc_dir) File "/usr/share/autotest/tests/depcheck/depcheck_lib.py", line 352, in do_depcheck (r, problems) = y.resolveDeps() File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 855, in resolveDeps CheckDeps, checkinstalls, checkremoves, missing = self._resolveRequires(errors) File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 984, in _resolveRequires thisneeds = self._checkInstall(txmbr) File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 1051, in _checkInstall oldreqs.extend(oldpo.returnPrco('strong_requires')) File "/usr/lib/python2.7/site-packages/yum/sqlitesack.py", line 385, in returnPrco if isinstance(self.prco[prcotype], tuple): KeyError: 'strong_requires' }}} http://autoqa- stg.fedoraproject.org/results/69597-autotest/virt26.qa/depcheck/results/f17 -updates-testing-.html http://autoqa- stg.fedoraproject.org/resultsdb/frontend/search?type=Testcase&terms=depcheck I suspect the problem is in updated yum. I see these crashes only on virt26 and virt27, which are F16 machines. It does not happen on qa06 and qa07, which are F15 machines. Also it does not seem to manifest on virt05, which is F16 machine but has an old yum. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/421> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 8

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel July 2012