[PATCH] Fedora 12 is EOL, remove it from repoinfo.conf
by Kamil Paral
---
repoinfo.conf | 18 ------------------
1 files changed, 0 insertions(+), 18 deletions(-)
diff --git a/repoinfo.conf b/repoinfo.conf
index e73a42a..4873302 100644
--- a/repoinfo.conf
+++ b/repoinfo.conf
@@ -57,21 +57,3 @@ url = %(updatesurl)s
parents = f13-updates, f13
collection_name = F-13
-# Fedora 12
-[f12]
-isactiverelease = yes
-path = 12
-url = %(goldurl)s
-collection_name = F-12
-
-[f12-updates]
-path = 12
-url = %(updatesurl)s
-parents = f12
-collection_name = F-12
-
-[f12-updates-testing]
-path = testing/12
-url = %(updatesurl)s
-parents = f12-updates, f12
-collection_name = F-12
--
1.7.3.2
13 years, 4 months
[PATCH 0/2] Remove anaconda and depcheck tests from master
by Kamil Paral
This patchset will remove anaconda and depcheck tests from master. They are
tracked in separate branches (liam and depcheck), we can merge them once
they are finished.
This replaces the need for '[PATCH] Disable execution of depcheck and anaconda until they are ready'.
Kamil Páral (2):
remove anaconda test and move it to a separate branch
remove depcheck test from master
tests/anaconda/dvd_install.py | 378 -----------------------------------------
tests/anaconda/ks.cfg | 54 ------
tests/depcheck/TODO | 17 --
tests/depcheck/depcheck | 251 ---------------------------
4 files changed, 0 insertions(+), 700 deletions(-)
delete mode 100755 tests/anaconda/dvd_install.py
delete mode 100755 tests/anaconda/ks.cfg
delete mode 100644 tests/depcheck/TODO
delete mode 100755 tests/depcheck/depcheck
--
1.7.3.2
13 years, 4 months
Re: [PATCH] return non-zero exit status when job scheduling fails
by Kamil Paral
----- "James Laska" <jlaska(a)redhat.com> wrote:
> On Tue, 2010-11-30 at 11:28 +0100, Kamil Páral wrote:
> > All the watchers and also the main autoqa script should return
> non-zero
> > exit code when job scheduling fails. This patch fixes that.
>
> Looks good, thanks! The only question I have is whether there
> something
> specific about exit_code 10?
Yes, it's greater than zero :-)
I picked it randomly, really. At first I wanted to return the number
of scheduled job failures as a return code (increment with each failure),
but than I realized it overflows at 256 (try to return 256 in Python and
you get 0 in the shell), and it was not really worth the effort to do
it this way. So... 10. :)
Pushed to master, thanks.
Kamil
13 years, 4 months
