On Wed, Apr 8, 2020 at 11:07 PM Amit Langote <amitlangote09@gmail.com> wrote:
> On Wed, Apr 8, 2020 at 9:21 PM Peter Eisentraut
> <peter.eisentraut@2ndquadrant.com> wrote:
> > I think this is because the END { } section in PostgresNode.pm shuts
> > down all running instances in immediate mode, which doesn't save
> > coverage properly.
>
> Thanks for that tip. Appending the following at the end of the test
> file has fixed the coverage reporting for me.
The patch posted in the previous email has it, but I meant this by
"the following":
+
+$node_publisher->stop('fast');
+$node_subscriber1->stop('fast');
+$node_subscriber2->stop('fast');
--
Amit Langote
EnterpriseDB: http://www.enterprisedb.com
