Mailinglist Archive: opensuse-project (146 mails)

< Previous Next >
Re: [opensuse-project] Proposal for a community based testing team
  • From: Stanislav Visnovsky <visnov@xxxxxxx>
  • Date: Wed, 25 Feb 2009 09:16:01 +0100
  • Message-id: <200902250916.01927.visnov@xxxxxxx>
On Streda 25 Február 2009 08:25:07 jdd wrote:
Gerald Pfeifer a écrit :
On Tue, 24 Feb 2009, jdd wrote:
Could it be possible to have asap a working distro (no blocking bugs
for the test team computers) to use on a dayly basis? most bugs are
unexpected ones :-).

What prevents you from using FACTORY?

(Serious question. If there is anything, we should address it.)

the problem is that factory is always changing, adding new bugs in the
time it remove old ones, so it's not possible to have the same
platform for all the test team. How can one validate a bug?

One thing I was trying to figure out is how to keep those bugs against Factory
valid for longer time. I want to avoid situation where a bug against Factory
is closed because nobody is able to reproduce it anymore, or even have no idea
how to reproduce it.

One suggestion I have is to use libzypp information. Do you know that if you
do 'zypper dup', libzypp will always store a testcase for this run? (I hope to
get it to keep more than one in future, but this is a start). Plus we have the
history now.

Testcase contains a snapshot of the repositories as well as the system
package-wise. So, it also contains information which packages were used when
the bug was triggered.

What we miss is an easy way how to dig that data and possibly to recreate the
situation.

Stano

--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups