NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commitb9164ea

committed

pg_amcheck: Keep trying to fix the tests.

Commit2418927 managed to removeone of the two places where we were checking for a "no such user"error while leaving the other one right next to it. So remove thattoo. In fact, remove the entire test, because the whole point ofthis test was to see which message we got on a failure.

1 parent2418927 commitb9164eaCopy full SHA for b9164ea

File tree

1 file changed

-10

lines changed

src/bin/pg_amcheck/t
- 002_nonesuch.pl

1 file changed

-10

lines changed

`‎src/bin/pg_amcheck/t/002_nonesuch.pl`

Lines changed: 1 addition & 10 deletions

Original file line number	Diff line number	Diff line change
`@@ -3,7 +3,7 @@`
`3`	`3`
`4`	`4`	`use PostgresNode;`
`5`	`5`	`use TestLib;`
`6`		`-use Test::Moretests=>75;`
	`6`	`+use Test::Moretests=>72;`
`7`	`7`
`8`	`8`	`# Test set-up`
`9`	`9`	`my ($node,$port);`
`@@ -71,15 +71,6 @@`
`71`	`71`	`[ ],`
`72`	`72`	`'checking with a non-existent user');`
`73`	`73`
`74`		`-# Failing to connect to the initial database due to bad username is an still an`
`75`		`-# error under --no-strict-names.`
`76`		`-$node->command_checks_all(`
`77`		`-['pg_amcheck','--no-strict-names','-U','no_such_user','postgres' ],`
`78`		`-1,`
`79`		`-[qr/^$/ ],`
`80`		`-[qr/role "no_such_user" does not exist/ ],`
`81`		`-'checking with a non-existent user under --no-strict-names');`
`82`		`-`
`83`	`74`	`#########################################`
`84`	`75`	`# Test checking databases without amcheck installed`
`85`	`76`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commitb9164ea

File tree

1 file changed

1 file changed

`‎src/bin/pg_amcheck/t/002_nonesuch.pl`

0 commit comments