You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Peter Eisentraut c538592959 Make all Perl warnings fatal ... There are a lot of Perl scripts in the tree, mostly code generation and TAP tests. Occasionally, these scripts produce warnings. These are probably always mistakes on the developer side (true positives). Typical examples are warnings from genbki.pl or related when you make a mess in the catalog files during development, or warnings from tests when they massage a config file that looks different on different hosts, or mistakes during merges (e.g., duplicate subroutine definitions), or just mistakes that weren't noticed because there is a lot of output in a verbose build. This changes all warnings into fatal errors, by replacing use warnings; by use warnings FATAL => 'all'; in all Perl files. Discussion: https://www.postgresql.org/message-id/flat/06f899fd-1826-05ab-42d6-adeb1fd5e200%40eisentraut.org		2 years ago
..
001_verify_heapam.pl	Make all Perl warnings fatal	2 years ago
002_cic.pl	Make all Perl warnings fatal	2 years ago
003_cic_2pc.pl	Make all Perl warnings fatal	2 years ago
004_verify_nbtree_unique.pl	Make all Perl warnings fatal	2 years ago
005_pitr.pl	Make all Perl warnings fatal	2 years ago