From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org> To: tarantool-patches@dev.tarantool.org, lvasiliev@tarantool.org Cc: Sergey Bronnikov <estetus@gmail.com>, alexander.turenko@tarantool.org Subject: [Tarantool-patches] [PATCH v1 0/4] Support Python 3 in Tarantool tests Date: Wed, 13 Jan 2021 11:48:28 +0300 [thread overview] Message-ID: <cover.1610526975.git.estetus@gmail.com> (raw) From: Sergey Bronnikov <estetus@gmail.com> It's another part of fixes related to Python 3 support. First one was here [1]. I haven't create new issue because the task is the same - switch test suite to Python 3, so two related commits in a patch series marked with "Part of #5538" and no one commit closes any task as it is required by guidelines. To test fixes one can use test-run's branch with Python 3 support [2]. 1. https://lists.tarantool.org/pipermail/tarantool-patches/2020-December/021151.html 2. https://github.com/tarantool/test-run/pull/263 Issue: https://github.com/tarantool/tarantool/issues/5538 (closed) Gitlab CI: https://gitlab.com/tarantool/tarantool/-/pipelines/240927581 Sergey Bronnikov (4): test: fix app-tap/http_client.test.lua test: fix xlog-py/big_lsn.test.py test: enable SO_REUSEADDR on socket in httpd.py test: enable disabled testcases back test/app-tap/http_client.test.lua | 6 +----- test/app-tap/httpd.py | 21 +++++++++++---------- test/xlog-py/big_lsn.test.py | 3 ++- 3 files changed, 14 insertions(+), 16 deletions(-) -- 2.25.1
next reply other threads:[~2021-01-13 8:48 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-13 8:48 Sergey Bronnikov via Tarantool-patches [this message] 2021-01-13 8:48 ` [Tarantool-patches] [PATCH v1 1/4] test: fix app-tap/http_client.test.lua Sergey Bronnikov via Tarantool-patches 2021-01-14 8:47 ` Leonid Vasiliev via Tarantool-patches 2021-01-14 9:50 ` Sergey Bronnikov via Tarantool-patches 2021-01-14 12:23 ` Alexander Turenko via Tarantool-patches 2021-01-14 12:52 ` Sergey Bronnikov via Tarantool-patches 2021-01-14 12:57 ` Alexander Turenko via Tarantool-patches 2021-01-13 8:48 ` [Tarantool-patches] [PATCH v1 2/4] test: fix xlog-py/big_lsn.test.py Sergey Bronnikov via Tarantool-patches 2021-01-14 9:02 ` Leonid Vasiliev via Tarantool-patches 2021-01-14 9:51 ` Sergey Bronnikov via Tarantool-patches 2021-01-14 12:38 ` Alexander Turenko via Tarantool-patches 2021-01-14 12:52 ` Sergey Bronnikov via Tarantool-patches 2021-01-13 8:48 ` [Tarantool-patches] [PATCH v1 3/4] test: enable SO_REUSEADDR on socket in httpd.py Sergey Bronnikov via Tarantool-patches 2021-01-13 19:59 ` Cyrill Gorcunov via Tarantool-patches 2021-01-14 9:09 ` Leonid Vasiliev via Tarantool-patches 2021-01-14 9:57 ` Sergey Bronnikov via Tarantool-patches 2021-01-14 12:51 ` Alexander Turenko via Tarantool-patches 2021-01-13 8:48 ` [Tarantool-patches] [PATCH v1 4/4] test: enable disabled testcases back Sergey Bronnikov via Tarantool-patches 2021-01-14 9:10 ` Leonid Vasiliev via Tarantool-patches 2021-01-13 20:03 ` [Tarantool-patches] [PATCH v1 0/4] Support Python 3 in Tarantool tests Cyrill Gorcunov via Tarantool-patches 2021-01-14 11:10 ` Leonid Vasiliev via Tarantool-patches 2021-01-15 9:34 ` Kirill Yukhin via Tarantool-patches
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=cover.1610526975.git.estetus@gmail.com \ --to=tarantool-patches@dev.tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=estetus@gmail.com \ --cc=lvasiliev@tarantool.org \ --cc=sergeyb@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v1 0/4] Support Python 3 in Tarantool tests' \ /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