June 2011 - autoqa-devel - Fedora Mailing-Lists

by Kamil Paral

AutoQA 0.5.0 has just been released and deployed. Package maintainers will see some notable changes. Please read the whole description here: http://kparal.wordpress.com/2011/06/29/autoqa-0-5-0-released/ Comments welcome. Kamil

12 years, 10 months

1
0
0 / 0

Merging master into stable - take 2

by Tim Flink

After the first botched attempt, I think that I got the merge done correctly without any differences to master or the new stable this time. If for some reason, you're interested - the code is up in the same github repo as before: https://github.com/tflink/autoqa-devel Instead of handling all the merge conflicts by hand, I found a vim plugin for git (fugitive) that made the process a lot easier and less vulnerable to human error: http://www.vim.org/scripts/script.php?script_id=2975 There is even a vimcast covering git merge resolving with fugitive: http://vimcasts.org/episodes/fugitive-vim-resolving-merge-conflicts-with-... Anyhow, it was more of an academic exercise at this point. The history is preserved after merge if you follow a specific file (git log --all --follow autoqa.spec for example). I captured that data for the fedorahosted repo [1] and my github repo [2]. Unfortunately, the graphs look horrible in either vim or firefox due to the way they're formatted but they look fine if you cat the files. I took screenshots of the git log graph for both the fedorahosted repo [1] and my github repo [2] (note that for the github graph, origin is github and upstream is fedorahosted). They do look different but I think that I created them the same way (QGit, same top and bottom). Tim [1] http://tflink.fedorapeople.org/autoqa/git_merge/fedorahosted_followspec [2] http://tflink.fedorapeople.org/autoqa/git_merge/github_followspec [3] http://tflink.fedorapeople.org/autoqa/git_merge/fedorahosted_graph.png [4] http://tflink.fedorapeople.org/autoqa/git_merge/github_graph.png

12 years, 10 months

1
0
0 / 0

Odd Depcheck Output

by Tim Flink

I was looking through some of the results on the testing instance and I found an ... interesting depcheck log. http://10.11.230.168/results/13591-autotest/hp-xw9300.test.redhat.com/dep... I'm still not quite sure what happened here but the only real error that I'm seeing offhand is in qterm even though a lot of builds were failed along with it. The timing of this isn't great but I'm starting to question the wisdom of the "fix" for #284 [1]. I had not anticipated extranious failures like this and I'm wondering if this is just going to cause more confusion than test results that aren't reported to bodhi. Thoughts? Tim [1] https://fedorahosted.org/autoqa/ticket/284

12 years, 10 months

4
7
0 / 0

[AutoQA] #326: Create user-facing documentation for depcheck

by fedora-badges

#326: Create user-facing documentation for depcheck ---------------------------+------------------------------------------------ Reporter: tflink | Owner: Type: task | Status: new Priority: major | Milestone: 0.5.0 Component: documentation | Keywords: ---------------------------+------------------------------------------------ Create a wiki page for depcheck that contains the following: * Thorough description of the test * How to read and interpret results * How to interpret the log output and use it to find failures * Description of common failures * Links to useful resources * correct procedure descriptions (e.g. packaging guidelines, etc). * Other relevant information {{{ #!comment For some reason, I can't get a ticket query with single result to render, changed to static }}} Related to #317 - Create user-facing documentation for upgradepath -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/326> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

12 years, 10 months

1
6
0 / 0

0.5.0 Release TODO

by Tim Flink

These are the things that I can think of that still need to be done before we release 0.5.0: NEWS/CHANGELOG (jdulaney) Git tagging and updating (tflink, kparal) Spec file update (jlaska) Announcements (?) Final Doc Check (everyone) Please correct me if I missed or misunderstood anything. Tim

12 years, 10 months

5
15
0 / 0

[AutoQA] #342: Prevent duplicate tests from being scheduled

by fedora-badges

#342: Prevent duplicate tests from being scheduled ----------------------+----------------------------------------------------- Reporter: tflink | Owner: Type: defect | Status: new Priority: major | Milestone: 0.5.0 Component: watchers | Keywords: ----------------------+----------------------------------------------------- We currently have an issue where tests are being scheduled more than once. This creates extra noise for maintainers and is a waste of resources - it should be fixed. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/342> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

12 years, 10 months

1
9
0 / 0

[AutoQA] #314: Decrease the volume of 'PASSED' email sent to maintainers from bodhi

by fedora-badges

#314: Decrease the volume of 'PASSED' email sent to maintainers from bodhi --------------------+------------------------------------------------------- Reporter: tflink | Owner: Type: task | Status: new Priority: major | Milestone: Hot issues Component: core | Keywords: --------------------+------------------------------------------------------- With the current setup, maintainers are sent an email with every single comment made by AutoQA. These emails aren't particularly useful and increase the amount of noise that maintainers need to filter out. Find a way to decrease the number of useless emails sent to maintainers. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/314> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

12 years, 10 months

1
14
0 / 0

[AutoQA] #344: Update repoinfo.conf - Remove release

by fedora-badges

#344: Update repoinfo.conf - Remove release ------------------------+--------------------------------------------------- Reporter: ausil | Owner: Type: task | Status: new Priority: critical | Milestone: Hot issues Component: production | Keywords: ------------------------+--------------------------------------------------- f13 is now eol -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/344> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

12 years, 10 months

1
2
0 / 0

AutoQA to test update with yum and PackageKit

by Athmane Madjoudj

Hello, There's a talk about AutoQA being able to test update with yum and PackageKit (pkcon), afaik it is not true, can someone from AutoQA team comment about this. https://bugzilla.redhat.com/show_bug.cgi?id=716752#c4 -- Athmane Madjoudj

12 years, 10 months

2
1
0 / 0

Autotest 0.13.0 released!

by Lucas Meneghel Rodrigues

After months of development, we are proud to announce a new release of autotest, 0.13.0. What is autotest? Autotest is a framework for fully automated testing. It is designed primarily to test the Linux kernel, though it is useful for many other purposes such as qualifying new hardware, virtualization testing and general user space program testing under linux platforms. It's an open-source project under the GPL and is used and developed by a number of organizations, including Google, IBM, Red Hat, and many others. You can see results of kernel test runs on http://test.kernel.org/tko/ Release repository: http://test.kernel.org/releases/0.13.0/ Release notes: http://autotest.kernel.org/wiki/Release0.13.0 Autotest project main page: http://autotest.kernel.org/ Want to hack on autotest? Please refer to: http://autotest.kernel.org/wiki/DownloadSource http://test.kernel.org/cgi-bin/mailman/listinfo/autotest Please report any issues on our bug tracking system: http://autotest.kernel.org/newticket In order to be able to open tickets on our bug tracking system, refer to: http://autotest.kernel.org/wiki/SiteAminContact

12 years, 10 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel June 2011