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

test: flaky config-luatest/isolated_mode_test.lua #332

Open
Totktonada opened this issue Nov 25, 2024 · 0 comments
Open

test: flaky config-luatest/isolated_mode_test.lua #332

Totktonada opened this issue Nov 25, 2024 · 0 comments
Assignees

Comments

@Totktonada
Copy link
Member

Test config-luatest/isolated_mode_test.lua is flaky.

  • branch: master
  • OS: Linux
  • Architecture: amd64
  • gc64: on
  • details: ASAN builds
[002] config-luatest/isolated_mode_test.lua                         [ fail ]
[002] Test failed! Output from reject file /tmp/t/rejects/config-luatest/isolated_mode.reject:
[002] Tarantool version is 3.3.0-entrypoint-77-g0afc929
[002] TAP version 13
[002] 1..10
[002] # Started on Mon Nov 25 11:46:30 2024
[002] # Starting group: config-luatest.isolated_mode
[002] ok     1	config-luatest.isolated_mode.test_startup_no_snap
[002] ok     2	config-luatest.isolated_mode.test_startup_with_snap
[002] ok     3	config-luatest.isolated_mode.test_read_only
[002] ok     4	config-luatest.isolated_mode.test_iproto_stop
[002] ok     5	config-luatest.isolated_mode.test_iproto_stop_failure
[002] not ok 6	config-luatest.isolated_mode.test_iproto_stop_failure_on_startup
[002] #   ...-ee/tarantool/test/config-luatest/isolated_mode_test.lua:368: expected 
[002] #   {
[002] #       alerts = {
[002] #           {
[002] #               message = "The isolated mode is set for the instance \"i-001\"",
[002] #               timestamp = "2024-11-25T11:48:02.344362Z",
[002] #               type = "warn",
[002] #           },
[002] #       },
[002] #       hierarchy = {group = "group-001", instance = "i-001", replicaset = "replicaset-001"},
[002] #       meta = {},
[002] #       status = "check_warnings",
[002] #   } to cover 
[002] #   {
[002] #       alerts = {
[002] #           {
[002] #               message = "The isolated mode is set for the instance \"i-001\"",
[002] #               type = "warn",
[002] #           },
[002] #           {
[002] #               message = "isolated mode: can't drop iproto connections during 0 seconds (continued in background): timed out",
[002] #               type = "warn",
[002] #           },
[002] #       },
[002] #   }
[002] #   stack traceback:
[002] #   	...-ee/tarantool/test/config-luatest/isolated_mode_test.lua:368: in function 'retrying'
[002] #   	...-ee/tarantool/test/config-luatest/isolated_mode_test.lua:366: in function 'retrying'
[002] #   	...-ee/tarantool/test/config-luatest/isolated_mode_test.lua:336: in function 'config-luatest.isolated_mode.test_iproto_stop_failure_on_startup'
[002] #   artifacts:
[002] #   	i-001 -> /tmp/t/002_config-luatest/artifacts/i-001-GhsGHTgNOLi0
[002] ok     7	config-luatest.isolated_mode.test_replication_to
[002] ok     8	config-luatest.isolated_mode.test_replication_from
[002] ok     9	config-luatest.isolated_mode.test_alert
[002] ok     10	config-luatest.isolated_mode.test_alert_on_startup
[002] # Ran 10 tests in 116.396 seconds, 9 succeeded, 1 failed
[002] 
[002] [test-run server "luatest_server"] Last 15 lines of the log file /tmp/t/002_config-luatest/isolated_mode_test.log:
[002] started logging into a pipe, SIGHUP log rotation disabled
[002] started logging into a pipe, SIGHUP log rotation disabled
[002] started logging into a pipe, SIGHUP log rotation disabled
[002] Test "config-luatest/isolated_mode_test.lua", conf: "None"
[002] 	failed, rerunning ...
Totktonada added a commit to Totktonada/tarantool that referenced this issue Nov 25, 2024
It shouldn't affect other developers. I'll look into it in background.
Filed issue tarantool/tarantool-qa#332 as a reminder.

Follows up tarantool#10796
Related to tarantool/tarantool-qa#332

NO_DOC=testing adjustment
NO_CHANGELOG=see NO_DOC
@Totktonada Totktonada self-assigned this Nov 25, 2024
Totktonada added a commit to tarantool/tarantool that referenced this issue Nov 25, 2024
It shouldn't affect other developers. I'll look into it in background.
Filed issue tarantool/tarantool-qa#332 as a reminder.

Follows up #10796
Related to tarantool/tarantool-qa#332

NO_DOC=testing adjustment
NO_CHANGELOG=see NO_DOC
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant