libtest-nowarnings-perl 1.06-ok2 source package in openKylin

Changelog

libtest-nowarnings-perl (1.06-ok2) yangtze; urgency=medium

  * Modify debian/control.

 -- denghao <email address hidden>  Fri, 16 Sep 2022 10:57:24 +0300

Upload details

Uploaded by:
denghao
Sponsored by:
Cibot
Uploaded to:
Yangtze V1.0
Original maintainer:
Openkylin Developers
Architectures:
all
Section:
perl
Urgency:
Medium Urgency

Publishing See full publishing history

Series Pocket Published Component Section
Nile V2.0 proposed main perl
Nile V2.0 release main perl
Yangtze V1.0 release main perl
Yangtze V1.0 proposed main perl

Downloads

File Size SHA-256 Checksum
libtest-nowarnings-perl_1.06.orig.tar.gz 19.0 KiB c2dc51143b7eb63231210e27df20d2c8393772e0a333547ec8b7a205ed62f737
libtest-nowarnings-perl_1.06-ok2.debian.tar.xz 9.9 KiB 32e31b1f063600e7ef686e4a1549441dad7d1300fe355a9af28e22f0b51ef80d
libtest-nowarnings-perl_1.06-ok2.dsc 1.9 KiB 3fd5aea378c8ac8f4fc0c7dbc7fec7d68d066370b1f6cea2d4211a64db4fac2e

Available diffs

View changes file

Binary packages built by this source

libtest-nowarnings-perl: module to make sure you didn't emit any warnings while testing

 In general, your tests shouldn't produce warnings. This module causes any
 warnings to be captured and stored. It automatically adds an extra test that
 will run when your script ends to check that there were no warnings. If there
 were any warnings, the test will give a "not ok" and diagnostics of where, when
 and what the warning was, including a stack trace of what was going on when
 it occurred.
 .
 If some of your tests are supposed to produce warnings then you should be
 capturing and checking them with Test::Warn, that way Test::NoWarnings will
 not see them and so not complain.
 .
 The test is run by an END block in Test::NoWarnings. It will not be run when
 any forked children exit.