pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: A failure of standby to follow timeline switch
Date: Sat, 26 Dec 2020 02:15:06 +0900
Message-ID: <a8bc5939-1c88-e35c-166a-6ef07f06dd83@oss.nttdata.com> (raw)
In-Reply-To: <20201225.120357.1120226009091644641.horikyota.ntt@gmail.com>
References: <20201209.174314.282492377848029776.horikyota.ntt@gmail.com>
	<697adab0-a3fe-e1cb-436b-3a8eaa9a2266@oss.nttdata.com>
	<20201225.120357.1120226009091644641.horikyota.ntt@gmail.com>



On 2020/12/25 12:03, Kyotaro Horiguchi wrote:
> 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.

What happens if you run make check-world with -j 4? When I ran that,
the test failed. But with -j 1, the test finished with success. I'm not sure
why this happened, though..

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION





view thread (18+ messages)  latest in thread

Message-ID: <a8bc5939-1c88-e35c-166a-6ef07f06dd83@oss.nttdata.com>
Permalink:  ../a8bc5939-1c88-e35c-166a-6ef07f06dd83@oss.nttdata.com/
Also on:    postgresql.org/message-id/a8bc5939-1c88-e35c-166a-6ef07f06dd83@oss.nttdata.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: masao.fujii@oss.nttdata.com, horikyota.ntt@gmail.com, pgsql-hackers@lists.postgresql.org
  Subject: Re: A failure of standby to follow timeline switch
  In-Reply-To: <a8bc5939-1c88-e35c-166a-6ef07f06dd83@oss.nttdata.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox