Re: A failure of standby to follow timeline switch

Поиск
Список
Период
Сортировка
От Kyotaro Horiguchi
Тема Re: A failure of standby to follow timeline switch
Дата
Msg-id 20201225.120357.1120226009091644641.horikyota.ntt@gmail.com
обсуждение исходный текст
Ответ на Re: A failure of standby to follow timeline switch  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Ответы Re: A failure of standby to follow timeline switch  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Список pgsql-hackers
Thank you for looking this.

At Thu, 24 Dec 2020 15:33:04 +0900, Fujii Masao <masao.fujii@oss.nttdata.com> wrote in 
> When I applied two patches in the master branch and
> ran "make check-world", I got the following error.
> 
> ============== creating database "contrib_regression" ==============
> # Looks like you planned 37 tests but ran 36.
> # Looks like your test exited with 255 just after 36.
> t/001_stream_rep.pl ..................
> Dubious, test returned 255 (wstat 65280, 0xff00)
> Failed 1/37 subtests
> ...
> Test Summary Report
> -------------------
> t/001_stream_rep.pl                (Wstat: 65280 Tests: 36 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: Bad plan.  You planned 37 tests but ran 36.
> Files=21, Tests=239, 302 wallclock secs ( 0.10 usr 0.05 sys + 41.69
> cusr 39.84 csys = 81.68 CPU)
> Result: FAIL
> make[2]: *** [check] Error 1
> make[1]: *** [check-recovery-recurse] Error 2
> make[1]: *** Waiting for unfinished jobs....
> t/070_dropuser.pl ......... ok

Mmm. I retried that and saw it succeed (with 0002 applied).

If I modified "user Test::More tests => 37" to 38 in the perl file, I
got a similar result.

> t/001_stream_rep.pl .. 37/38 # Looks like you planned 38 tests but ran 37.
> t/001_stream_rep.pl .. Dubious, test returned 255 (wstat 65280, 0xff00)
> Failed 1/38 subtests 
> 
> Test Summary Report
> -------------------
> t/001_stream_rep.pl (Wstat: 65280 Tests: 37 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: Bad plan.  You planned 38 tests but ran 37.
> Files=1, Tests=37, 10 wallclock secs ( 0.03 usr  0.00 sys +  3.64 cusr  2.05 csy
> s =  5.72 CPU)
> Result: FAIL
> make: *** [Makefile:19: check] Error 1

I can't guess what happenened on your environment..

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Justin Pryzby
Дата:
Сообщение: Re: New Table Access Methods for Multi and Single Inserts
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: Deadlock between backend and recovery may not be detected