Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[backport 2.11] test: increase timeouts in on_shutdown tests #9712

Merged

Conversation

sergepetrenko
Copy link
Collaborator

Backporting PR #9481 to 2.11 to fix the same issue there. Below is the original commit mesage.

I got four fails on the given tests in a row on debug-asan job in CI for tarantool-ee.

It seems, tarantool-ee is more sensitive to small timeouts, when the address sanitizer slows down the execution. Or I'm just lucky.

Anyway, the given tests don't really need small timeouts: increasing it doesn't break any test logic, doesn't increase duration of the test in a successful case and doesn't increase it in case of a failure.

The tests are more stable after the change: I verified it locally by running each of the tests in parallel many times on tarantool built with enabled address sanitizer.

See the following commits for details about the given test cases and the problems behind.

  • commit 1fcfb8c ("app: start init script event loop explicitly")
  • commit 786eb2a ("main: don't break graceful shutdown on init script exit")

Follows up #9266
Follows up #9411

NO_DOC=test adjustment
NO_CHANGELOG=see NO_DOC

(cherry picked from commit dfca3c6)

I got four fails on the given tests in a row on debug-asan job in CI for
tarantool-ee.

It seems, tarantool-ee is more sensitive to small timeouts, when the
address sanitizer slows down the execution. Or I'm just lucky.

Anyway, the given tests don't really need small timeouts: increasing it
doesn't break any test logic, doesn't increase duration of the test in a
successful case and doesn't increase it in case of a failure.

The tests are more stable after the change: I verified it locally by
running each of the tests in parallel many times on tarantool built with
enabled address sanitizer.

See the following commits for details about the given test cases and the
problems behind.

* commit 1fcfb8c ("app: start init script event loop explicitly")
* commit 786eb2a ("main: don't break graceful shutdown on init
  script exit")

Follows up tarantool#9266
Follows up tarantool#9411

NO_DOC=test adjustment
NO_CHANGELOG=see NO_DOC

(cherry picked from commit dfca3c6)
@sergepetrenko sergepetrenko self-assigned this Feb 19, 2024
@sergepetrenko sergepetrenko requested a review from a team as a code owner February 19, 2024 07:05
@sergepetrenko sergepetrenko added the full-ci Enables all tests for a pull request label Feb 19, 2024
@coveralls
Copy link

Coverage Status

coverage: 85.807% (+0.009%) from 85.798%
when pulling 10b6465 on sergepetrenko:on-shutdown-timeout-2.11
into 9dc3490
on tarantool:release/2.11
.

@sergepetrenko sergepetrenko merged commit 1604a97 into tarantool:release/2.11 Feb 19, 2024
161 checks passed
@sergepetrenko sergepetrenko deleted the on-shutdown-timeout-2.11 branch April 4, 2024 11:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
full-ci Enables all tests for a pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants