Differences between revisions 65 and 66
⇤ ← Revision 65 as of 2009-09-03 05:19:33 →
Size: 4365
Editor: LarsWirzenius
Comment:
← Revision 66 as of 2010-01-05 01:48:41 → ⇥
Size: 3320
Editor: HolgerLevsen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
= General info = = Overview about piuparts =
Line 11: Line 11:
piuparts is being run constantly on [[http://piuparts.debian.org|piuparts.debian.org]] - that URL links to more general information about piuparts too.

A [[http://wiki.debian.org/piuparts/FAQ|FAQ]] is also available.		 piuparts is being run constantly on the main archive, the results are public on [[http://piuparts.debian.org|piuparts.debian.org]]. piuparts itself has a [[http://piuparts.debian.org/doc/README.html|README]] and a [[http://piuparts.debian.org/doc/piuparts.1.html|piuparts manpage]], for the piuparts.debian.org setup there is also an [[http://wiki.debian.org/piuparts/FAQ|FAQ]] available. Below is an overview of information not covered elsewhere.
Line 29: Line 27:
 * stalled
 * planning stage		  * stalled at planning stage
Line 32: Line 29:
 * will take at least a year until piuparts1 becomes obsolete
Line 48: Line 44:
Once a day at midnight UTC piuparts-reports is run as piupartsm by cron to generate the html output of the logs. Once a day piuparts-reports is run as piupartsm by cron to generate the html output of the logs.
Line 54: Line 50:
 * piuparts.cs.helsinki.fi aka [[http://db.debian.org/machines.cgi?host=piatti|piatti.debian.org]] aka piuparts.debian.org  piuparts.cs.helsinki.fi aka [[http://db.debian.org/machines.cgi?host=piatti|piatti.debian.org]] aka piuparts.debian.org
Line 60: Line 56:
 * currently captabable of testing sid in 3 days and squeeze in 12. using schroot and lvm snaspshots this can be improved, but filing bugs and adding more tests (see the bts...) is more important and interesting today for me.
Line 65: Line 62:
= Piuparts and PTS integration suggestion =

/!\ this specification has been implemented but a simpler one. This notes are kept here for reference and shall be deleted soon.

In order for the PTS to be able to display piuparts testing status for a package, and link to its log file,
Piuparts could generate a set of static files that will be visible via http:

{{{
%s = source package name
%v = source package version

/source/%s -> index page
/source/%s/%v -> a particular log
/source/%s/latest -> log for latest version
/source/%s/piuparts-%p/%v -> a particular log from a version of piuparts

similar for /binary-$ARCH/

/%s -> /source/%s

For PTS integration: one file with results for all source packages:
/results-per-source.txt
    %s pass $MATCHINGLOG
    %s fail $MATCHINGLOG
    %s fuzzy $URLto_stats_page ([http://piuparts.debian.org/squeeze/state-waiting-for-dependency-to-be-tested.html example page])

And really unknown, ie not listed in that file.


The earlier idea of having the piuparts version included there has been overthrown: on new tests, the successful test shall be reseted. The version is in the log anyway :)

}}}

{{{

For Ubuntu development weather report (similar to PTS): a file with the following:
    Pass: %d
    Fail: %d

}}}

(See https://blueprints.launchpad.net/ubuntu/+spec/developer-weather-report for the Ubuntu developer weather report.)

Contents

  1. Overview about piuparts
  2. Developing piuparts
  3. Developing piuparts, the rewrite of version 2
    1. From the BoF at Debconf9
  4. How piuparts is setup on piuparts.debian.org
    1. Machine info
  5. Howto setup a piuparts test-instance for development

Overview about piuparts

Description: .deb package installation, upgrading, and removal testing tool

piuparts is being run constantly on the main archive, the results are public on piuparts.debian.org. piuparts itself has a README and a piuparts manpage, for the piuparts.debian.org setup there is also an FAQ available. Below is an overview of information not covered elsewhere.

Developing piuparts

Developing piuparts, the rewrite of version 2

From the BoF at Debconf9

How piuparts is setup on piuparts.debian.org

Running piuparts is the boring, automated part and is supervised by Luk and Holger, who can su into the piupartss (slave) user. piuparts-slave is run in a shared screen session and seldom needs interaction. The piupartss user needs to be able to run piuparts and thus can use sudo without restrictions.

The slave automatically starts the master, to reserve packages to process and to pass logfiles to the master.

Ideally all members of the Debian-QA group can su to the piupartsm user and process the logfiles - currently it's again only Luk and Holger. piupartsm has no special privileges. If you want to help, please join #debian-qa and say so there.

Once a day piuparts-reports is run as piupartsm by cron to generate the html output of the logs.

For more information see http://svn.debian.org/viewsvn/piuparts/piatti/README.txt

Machine info

  • piuparts.cs.helsinki.fi aka piatti.debian.org aka piuparts.debian.org

  • hosted at Department of Computer Science, University of Helsinki

  • donated by HP

  • dual AMD Opteron(tm) Processor 275, 2.2 Ghz
  • 8GB RAM
  • 300 GB physical volume for data
  • currently captabable of testing sid in 3 days and squeeze in 12. using schroot and lvm snaspshots this can be improved, but filing bugs and adding more tests (see the bts...) is more important and interesting today for me.

Howto setup a piuparts test-instance for development

*to be written*

CategoryPermalink