Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Yukhin <kyukhin@tarantool.org>
To: "Alexander V. Tikhonov" <avtikhon@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v1] test: move error messages into logs
Date: Thu, 10 Dec 2020 14:44:45 +0000	[thread overview]
Message-ID: <20201210144445.222emia5y5p4b5sl@tarantool.org> (raw)
In-Reply-To: <58584e4677c66eb40e7ea504382df39be2d5ffef.1607442267.git.avtikhon@tarantool.org>

Hello,

On 08 Dec 18:49, Alexander V. Tikhonov wrote:
> Cc: tarantool-patches@dev.tarantool.org
> 
> Found that some tests on fail use box.info* calls to print information,
> like:
> 
>   [024] --- replication/wal_rw_stress.result	Mon Nov 30 10:02:43 2020
>   [024] +++ var/rejects/replication/wal_rw_stress.reject	Sun Dec  6 16:06:46 2020
>   [024] @@ -77,7 +77,45 @@
>   [024]              r.downstream.status ~= 'stopped')    \
>   [024]  end) or box.info
>   [024]  ---
>   [024] -- true
>   [024] +- version: 2.7.0-109-g0b3ad5d8a0
>   [024] +  id: 2
>   [024] +  ro: false
>   [024] +  uuid: e0b8863f-7b50-4eb5-947f-77f92c491827
> 
> It denies test-run from rerunng these tests using checksums, because
> of changing output on each fail, like 'version:' either 'uuid:' fields
> values above. To avoid of it, these calls outputs should be redirected
> to log files using log.error(). Also the same fix made for tests with
> fio.listdir() and fio.stat() on errors.
> ---
> 
> Github: https://github.com/tarantool/tarantool/tree/avtikhon/tests-output-to-logs

I've checked your patch into 1.10, 2.5, 2.6 and master.

--
Regards, Kirill Yukhin

      reply	other threads:[~2020-12-10 14:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 15:49 Alexander V. Tikhonov
2020-12-10 14:44 ` Kirill Yukhin [this message]

Reply instructions:

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

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

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201210144445.222emia5y5p4b5sl@tarantool.org \
    --to=kyukhin@tarantool.org \
    --cc=avtikhon@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v1] test: move error messages into logs' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox