Re: piuparts output wishlist?
pe, 2009-07-03 kello 11:39 +0200, Peter Pöschl kirjoitti: What about emitting this as TAP, the Test Anything Protocol [1]? That is a very interesting suggestion. I don't think it looks very good for human consumption, but I would love to have a plugin to optionally produce it for situations where computers can make use of it. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: piuparts output wishlist?
Lars Wirzenius l...@liw.fi writes: How would _you_ like to see piuparts report results, and produce other output? Go wild, the sky is bright blue. The obvious things to fix are: - make it really easy to see what the result of each test is Almost as obvious is to easily identify which test is being run. I think a good way to show both of these would be to have a different channel of output, beside the logging output, that shows explicitly a test identifier at the start, and then the result of that test at the end, with a visually similar presentation for both. “Test identifier” can simply be a command line, for example:: N: Running command: ‘dpkg --info /var/cache/pbuilder/result/burn_0.4.4-1_all.deb’ … I: Command OK: ‘dpkg --info /var/cache/pbuilder/result/burn_0.4.4-1_all.deb’ N: Running command: ‘chroot /tmp/tmpQm3zr8 dpkg -i tmp/burn_0.4.4-1_all.deb’ … E: Command FAILED: ‘chroot /tmp/tmpQm3zr8 dpkg -i tmp/burn_0.4.4-1_all.deb’ What about emitting this as TAP, the Test Anything Protocol [1]? The general format is 1..N ok 1 Description # Directive not ok 42 Description # Diagnostic It does not support severities, but these could be put in a Diagnostic line. [1] http://search.cpan.org/~petdance/TAP-1.00/TAP.pm Regards, Peter Pöschl -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: piuparts output wishlist?
Peter Pöschl pp2ml.deb0...@nest-ai.de writes: What about emitting this as TAP, the Test Anything Protocol [1]? +0 from me. Investigating TAP is on my to-do list, so I don't have an opinion on that yet; but in principle it seems fine, and there is goodness in widely-used output formats. -- \ “Anyone who believes exponential growth can go on forever in a | `\finite world is either a madman or an economist.” —Kenneth | _o__) Boulding | Ben Finney -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: piuparts output wishlist?
Lars Wirzenius l...@liw.fi writes: How would _you_ like to see piuparts report results, and produce other output? Go wild, the sky is bright blue. The obvious things to fix are: - make it really easy to see what the result of each test is Almost as obvious is to easily identify which test is being run. This is kind of available now, but only if you know to look in the ‘DEBUG’ messages for command starts and exit status reports. I think those debug messages are fine (provided the default logging level is raised so those messages don't appear by default). I think a good way to show both of these would be to have a different channel of output, beside the logging output, that shows explicitly a test identifier at the start, and then the result of that test at the end, with a visually similar presentation for both. “Test identifier” can simply be a command line, for example:: N: Running command: ‘dpkg --info /var/cache/pbuilder/result/burn_0.4.4-1_all.deb’ … I: Command OK: ‘dpkg --info /var/cache/pbuilder/result/burn_0.4.4-1_all.deb’ N: Running command: ‘chroot /tmp/tmpQm3zr8 dpkg -i tmp/burn_0.4.4-1_all.deb’ … E: Command FAILED: ‘chroot /tmp/tmpQm3zr8 dpkg -i tmp/burn_0.4.4-1_all.deb’ - indicate severity of test failures (an extra file after purge is not not as severe as leaving a daemon process running) I like the earlier suggestions of ‘I: ’, ‘N: ’, ‘W: ’, ‘E: ’ prefixes to indicate these severities. (I would understand these as, in increasing order of severity: “info”, “notice”, “warning”, “error”.) - make logs be rather less voluminous by default Yes, the default log output level should be something like ‘NOTICE’. -- \ “The most common way people give up their power is by thinking | `\ they don't have any.” —Alice Walker | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: piuparts output wishlist?
2009/6/20 Lars Wirzenius l...@liw.fi: I'm thinking about changing the way piuparts outputs results. At the moment it outputs a log file that contains everything it does, and buried deep in that is the test results. This tends to work badly. [...] How would _you_ like to see piuparts report results, and produce other output? Go wild, the sky is bright blue. I: Reading database ... 5834 files and directories currently installed. I: Removing bla bla ... I: Purging bla bla ... W: Suspicious action bla bla ... E: dpkg: error processing ucf (--remove) E: bla bla... Alternatively [I] Reading database ... 5834 files and directories currently installed. [I] Removing bla bla ... [I] Purging bla bla ... [W] Suspicious action bla bla ... [E] dpkg: error processing ucf (--remove) [E] bla bla... Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: piuparts output wishlist?
Jens Peter Secher j...@debian.org writes: 2009/6/20 Lars Wirzenius l...@liw.fi: I'm thinking about changing the way piuparts outputs results. At the moment it outputs a log file that contains everything it does, and buried deep in that is the test results. This tends to work badly. [...] How would _you_ like to see piuparts report results, and produce other output? Go wild, the sky is bright blue. I: Reading database ... 5834 files and directories currently installed. I: Removing bla bla ... I: Purging bla bla ... W: Suspicious action bla bla ... E: dpkg: error processing ucf (--remove) E: bla bla... Lintian uses N: for informational messages that don't represent problems. That's not any kind of standard, of course, but it might be worth copying it. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
