ke, 2006-04-05 kello 03:17 +0200, Jeroen van Wolffelaar kirjoitti:
> - A data repository. Currently in /org/qa.debian.org/rebuildtesting/{db,pool}
> on merkel. This repository should get some smarter indices, but
> basicly, the pool structure is most flexible and efficient, at the
> cost of a level of indirection if you want "all $foo from unstable".
I could use that for piuparts, but not directly. The workflow for
piuparts is currently as follows:
I have two machines that run piuparts tests, and one of them also acts
as the master that collects log files and decides what can be tested
next. Packages won't be tested until their dependencies have been tested
successfully. Log files are automatically sorted into "pass" and "fail"
categories (cunningly implemented as subdirectories), and when they
arrive at the master, I check the failed ones manually.
A piuparts test may fail for any of several reasons. One of them is
obviously that the package is buggy. The other reasons are to do with my
test setup (broken mirroring, broken machine, something stupid I
did...), bugs in piuparts, or something like the current X transition
that temporarily fails many tests.
These other reasons happen with some regularity, I don't think it is
useful at all to send up to a couple of hundred kilobytes of log files
per every new package in unstable every day somewhere for public
viewing. These other reasons are only interesting for the piuparts
"operator" (currently me), who can delete them after fixing things.
Thus, only the manually checked failed logs should be uploaded to this
repository.
A further complication is that there's often a need to re-test
everything, so there may well be multiple log files per package version.
For example, when I change something in piuparts, this may result in a
need to re-test everything that has already been tested successfully.
(I am open to suggestions on how to improve the piuparts workflow. In
fact, I'm going to have to re-think it anyway, since I want to open it
up for more people.)
> - A way to submit data into the repository. This works via email to
> [EMAIL PROTECTED], in a sepecific format.
I'd rather use HTTP (mail gets lost or arbitrarily delayed randomly)
and I would really prefer to have an option for compressed data. Even if
it is only 200 kB per package, the bandwidth wassteage is still
distasteful to me.
> Subject: Result for lintian libc6_2.3.6-4_i386 1.23.6 ok 1E9W0I
The syntax of the subject is not clear to me.
> - A web interface to actually query in some convenient way the database.
With piuparts, it would be interesting to people to see the state of
their package with regard to piuparts testing: is the package tested
successfully? unsuccessfully? is it ready to be tested and just waiting
for some free cpu cycles? waiting for a dependency to be tested first?
waiting for a dependency that failed testing? And so on, there's a bunch
of different states.
These don't really seem appropriate for the QA repository, though.
--
It's pointless to argue with someone with no soul. -- Skip Middleton
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
