-
Notifications
You must be signed in to change notification settings - Fork 387
test: flaky replication/election_qsync.test.lua test #5430
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
Labels
Comments
avtikhon
added a commit
that referenced
this issue
Oct 21, 2020
box/net.box_incorrect_iterator_gh-841.test.lua gh-5434 replication/election_basic.test.lua gh-5368 replication/election_qsync.test.lua gh-5430 replication/election_qsync_stress.test.lua gh-5395 replication/gh-4402-info-errno.test.lua gh-5366 replication/gh-5426-election-on-off.test.lua gh-5433 wal_off/snapshot_stress.test.lua gh-5431 t
avtikhon
added a commit
that referenced
this issue
Oct 21, 2020
box/net.box_incorrect_iterator_gh-841.test.lua gh-5434 replication/election_basic.test.lua gh-5368 replication/election_qsync.test.lua gh-5430 replication/election_qsync_stress.test.lua gh-5395 replication/gh-4402-info-errno.test.lua gh-5366 replication/gh-5426-election-on-off.test.lua gh-5433 wal_off/snapshot_stress.test.lua gh-5431
kyukhin
pushed a commit
that referenced
this issue
Oct 22, 2020
box/net.box_incorrect_iterator_gh-841.test.lua gh-5434 replication/election_basic.test.lua gh-5368 replication/election_qsync.test.lua gh-5430 replication/election_qsync_stress.test.lua gh-5395 replication/gh-4402-info-errno.test.lua gh-5366 replication/gh-5426-election-on-off.test.lua gh-5433 wal_off/snapshot_stress.test.lua gh-5431
kyukhin
pushed a commit
that referenced
this issue
Oct 22, 2020
box/net.box_incorrect_iterator_gh-841.test.lua gh-5434 replication/election_basic.test.lua gh-5368 replication/election_qsync.test.lua gh-5430 replication/election_qsync_stress.test.lua gh-5395 replication/gh-4402-info-errno.test.lua gh-5366 replication/gh-5426-election-on-off.test.lua gh-5433 wal_off/snapshot_stress.test.lua gh-5431 (cherry picked from commit c596d31)
kyukhin
pushed a commit
that referenced
this issue
Oct 22, 2020
box/net.box_incorrect_iterator_gh-841.test.lua gh-5434 replication/election_basic.test.lua gh-5368 replication/election_qsync.test.lua gh-5430 replication/election_qsync_stress.test.lua gh-5395 replication/gh-4402-info-errno.test.lua gh-5366 replication/gh-5426-election-on-off.test.lua gh-5433 wal_off/snapshot_stress.test.lua gh-5431 (cherry picked from commit c596d31)
kyukhin
pushed a commit
that referenced
this issue
Oct 22, 2020
box/net.box_incorrect_iterator_gh-841.test.lua gh-5434 replication/election_basic.test.lua gh-5368 replication/election_qsync.test.lua gh-5430 replication/election_qsync_stress.test.lua gh-5395 replication/gh-4402-info-errno.test.lua gh-5366 replication/gh-5426-election-on-off.test.lua gh-5433 wal_off/snapshot_stress.test.lua gh-5431 (cherry picked from commit c596d31)
avtikhon
added a commit
that referenced
this issue
Oct 22, 2020
avtikhon
added a commit
that referenced
this issue
Oct 31, 2020
Added flaky tests results files checksums: replication/gh-3160-misc-heartbeats-on-master-changes.test.lua gh-4940 replication/ddl.test.lua gh-5337 replication/election_qsync.test.lua gh-5430 replication/election_qsync_stress.test.lua gh-5395 replication/gh-5287-boot-anon.test.lua gh-5412 vinyl/deferred_delete.test.lua gh-5089 vinyl/iterator.test.lua gh-5336 vinyl/gh-4957-too-many-upserts.test.lua gh-5378 vinyl/gc.test.lua gh-5474
avtikhon
added a commit
that referenced
this issue
Oct 31, 2020
Added flaky tests results files checksums: box/hash_gh-1467.test.lua gh-5476 box-tap/session.storage.test.lua gh-5346 replication/gh-3160-misc-heartbeats-on-master-changes.test.> gh-4940 replication/ddl.test.lua gh-5337 replication/election_qsync.test.lua gh-5430 replication/election_qsync_stress.test.lua gh-5395 replication/gh-5287-boot-anon.test.lua gh-5412 vinyl/deferred_delete.test.lua gh-5089 vinyl/iterator.test.lua gh-5336 vinyl/gh-4957-too-many-upserts.test.lua gh-5378 vinyl/gc.test.lua gh-5474
avtikhon
added a commit
that referenced
this issue
Oct 31, 2020
Added flaky tests results files checksums: box/hash_gh-1467.test.lua gh-5476 box-tap/session.storage.test.lua gh-5346 replication/gh-3160-misc-heartbeats-on-master-changes.test.> gh-4940 replication/ddl.test.lua gh-5337 replication/election_qsync.test.lua gh-5430 replication/election_qsync_stress.test.lua gh-5395 replication/gh-5287-boot-anon.test.lua gh-5412 vinyl/deferred_delete.test.lua gh-5089 vinyl/gh-4957-too-many-upserts.test.lua gh-5378 vinyl/gc.test.lua gh-5474
avtikhon
added a commit
that referenced
this issue
Nov 1, 2020
Added flaky tests results files checksums: box/hash_gh-1467.test.lua gh-5476 box-tap/session.storage.test.lua gh-5346 replication/gh-3160-misc-heartbeats-on-master-changes.test.> gh-4940 replication/ddl.test.lua gh-5337 replication/election_qsync.test.lua gh-5430 replication/election_qsync_stress.test.lua gh-5395 replication/gh-5287-boot-anon.test.lua gh-5412 vinyl/deferred_delete.test.lua gh-5089 vinyl/gh-4957-too-many-upserts.test.lua gh-5378 vinyl/gh-5141-invalid-vylog-file.test.lua gh-5141 vinyl/gc.test.lua gh-5474 vinyl/iterator.test.lua gh-5141
avtikhon
added a commit
that referenced
this issue
Nov 1, 2020
Added flaky tests results files checksums: box/access.test.lua gh-5373 gh-5411 box/hash_gh-1467.test.lua gh-5476 box/net.box_incorrect_iterator_gh-841.test.lua gh-5434 box-tap/session.storage.test.lua gh-5346 replication/gh-3160-misc-heartbeats-on-master-changes.test.> gh-4940 replication/ddl.test.lua gh-5337 replication/election_qsync.test.lua gh-5430 replication/election_qsync_stress.test.lua gh-5395 replication/gh-5287-boot-anon.test.lua gh-5412 vinyl/deferred_delete.test.lua gh-5089 vinyl/gh-4957-too-many-upserts.test.lua gh-5378 vinyl/gh-5141-invalid-vylog-file.test.lua gh-5141 vinyl/gc.test.lua gh-5474 vinyl/iterator.test.lua gh-5141 Removed: replication/gh-5426-election-on-off.test.lua gh-5433
grafin
added a commit
to grafin/tarantool
that referenced
this issue
Mar 25, 2022
Covered most of box_promote and box_demote with tests: 1. Promote/demote unconfigured box 2. Promoting current leader with elections on and off 3. Demoting follower with elections on and off 4. Promoting current leader, but not limbo owner with elections on 5. Demoting current leader with elections on and off 6. Simultaneous promote/demote 7. Promoting voter 8. Interfering promote/demote while in wal delay 9. Interfering promote/demote while waiting for limbo to be emptied 10. Interfering promote while waiting for limbo to be acked (similar to replication/tarantoolgh-5430-qsync-promote-crash.test.lua) Didn’t find a way to test failing box_wait_limbo_acked in box_demote without adding dedicated ERRINJ. IMO box_wait_limbo_acked should be covered by its own tests. Closes tarantool#6033 NO_DOC=testing stuff NO_CHANGELOG=testing stuff
grafin
added a commit
to grafin/tarantool
that referenced
this issue
May 31, 2022
Covered most of box_promote and box_demote with tests: 1. Promote/demote unconfigured box 2. Promoting current leader with elections on and off 3. Demoting follower with elections on and off 4. Promoting current leader, but not limbo owner with elections on 5. Demoting current leader with elections on and off 6. Simultaneous promote/demote 7. Promoting voter 8. Interfering promote/demote while writing new term to wal 9. Interfering promote/demote while waiting for synchro queue to be emptied 10. Interfering promote while waiting for limbo to be acked (similar to replication/tarantoolgh-5430-qsync-promote-crash.test.lua) Closes tarantool#6033 NO_DOC=testing stuff NO_CHANGELOG=testing stuff
grafin
added a commit
to grafin/tarantool
that referenced
this issue
Jun 15, 2022
Covered most of box_promote and box_demote with tests: 1. Promote/demote unconfigured box 2. Promoting current leader with elections on and off 3. Demoting follower with elections on and off 4. Promoting current leader, but not limbo owner with elections on 5. Demoting current leader with elections on and off 6. Simultaneous promote/demote 7. Promoting voter 8. Interfering promote/demote while writing new term to wal 9. Interfering promote/demote while waiting for synchro queue to be emptied 10. Interfering promote while waiting for limbo to be acked (similar to replication/tarantoolgh-5430-qsync-promote-crash.test.lua) Closes tarantool#6033 NO_DOC=testing stuff NO_CHANGELOG=testing stuff
grafin
added a commit
to grafin/tarantool
that referenced
this issue
Jun 15, 2022
Covered most of box_promote and box_demote with tests: 1. Promote/demote unconfigured box 2. Promoting current leader with elections on and off 3. Demoting follower with elections on and off 4. Promoting current leader, but not limbo owner with elections on 5. Demoting current leader with elections on and off 6. Simultaneous promote/demote 7. Promoting voter 8. Interfering promote/demote while writing new term to wal 9. Interfering promote/demote while waiting for synchro queue to be emptied 10. Interfering promote while waiting for limbo to be acked (similar to replication/tarantoolgh-5430-qsync-promote-crash.test.lua) Closes tarantool#6033 NO_DOC=testing stuff NO_CHANGELOG=testing stuff
grafin
added a commit
to grafin/tarantool
that referenced
this issue
Jun 17, 2022
Covered most of box_promote and box_demote with tests: 1. Promote/demote unconfigured box 2. Promoting current leader with elections on and off 3. Demoting follower with elections on and off 4. Promoting current leader, but not limbo owner with elections on 5. Demoting current leader with elections on and off 6. Simultaneous promote/demote 7. Promoting voter 8. Interfering promote/demote while writing new term to wal 9. Interfering promote/demote while waiting for synchro queue to be emptied 10. Interfering promote while waiting for limbo to be acked (similar to replication/tarantoolgh-5430-qsync-promote-crash.test.lua) Closes tarantool#6033 NO_DOC=testing stuff NO_CHANGELOG=testing stuff
grafin
added a commit
to grafin/tarantool
that referenced
this issue
Jun 17, 2022
Covered most of box_promote and box_demote with tests: 1. Promote/demote unconfigured box 2. Promoting current leader with elections on and off 3. Demoting follower with elections on and off 4. Promoting current leader, but not limbo owner with elections on 5. Demoting current leader with elections on and off 6. Simultaneous promote/demote 7. Promoting voter 8. Interfering promote/demote while writing new term to wal 9. Interfering promote/demote while waiting for synchro queue to be emptied 10. Interfering promote while waiting for limbo to be acked (similar to replication/tarantoolgh-5430-qsync-promote-crash.test.lua) Closes tarantool#6033 NO_DOC=testing stuff NO_CHANGELOG=testing stuff
grafin
added a commit
to grafin/tarantool
that referenced
this issue
Jun 20, 2022
Covered most of box_promote and box_demote with tests: 1. Promote/demote unconfigured box 2. Promoting current leader with elections on and off 3. Demoting follower with elections on and off 4. Promoting current leader, but not limbo owner with elections on 5. Demoting current leader with elections on and off 6. Simultaneous promote/demote 7. Promoting voter 8. Interfering promote/demote while writing new term to wal 9. Interfering promote/demote while waiting for synchro queue to be emptied 10. Interfering promote while waiting for limbo to be acked (similar to replication/tarantoolgh-5430-qsync-promote-crash.test.lua) Closes tarantool#6033 NO_DOC=testing stuff NO_CHANGELOG=testing stuff
grafin
added a commit
to grafin/tarantool
that referenced
this issue
Jun 20, 2022
Covered most of box_promote and box_demote with tests: 1. Promote/demote unconfigured box 2. Promoting current leader with elections on and off 3. Demoting follower with elections on and off 4. Promoting current leader, but not limbo owner with elections on 5. Demoting current leader with elections on and off 6. Simultaneous promote/demote 7. Promoting voter 8. Interfering promote/demote while writing new term to wal 9. Interfering promote/demote while waiting for synchro queue to be emptied 10. Interfering promote while waiting for limbo to be acked (similar to replication/tarantoolgh-5430-qsync-promote-crash.test.lua) Closes tarantool#6033 NO_DOC=testing stuff NO_CHANGELOG=testing stuff
grafin
added a commit
to grafin/tarantool
that referenced
this issue
Jun 30, 2022
Covered most of box_promote and box_demote with tests: 1. Promote/demote unconfigured box 2. Promoting current leader with elections on and off 3. Demoting follower with elections on and off 4. Promoting current leader, but not limbo owner with elections on 5. Demoting current leader with elections on and off 6. Simultaneous promote/demote 7. Promoting voter 8. Interfering promote/demote while writing new term to wal 9. Interfering promote/demote while waiting for synchro queue to be emptied 10. Interfering promote while waiting for limbo to be acked (similar to replication/tarantoolgh-5430-qsync-promote-crash.test.lua) Closes tarantool#6033 NO_DOC=testing stuff NO_CHANGELOG=testing stuff
kyukhin
pushed a commit
that referenced
this issue
Jun 30, 2022
Covered most of box_promote and box_demote with tests: 1. Promote/demote unconfigured box 2. Promoting current leader with elections on and off 3. Demoting follower with elections on and off 4. Promoting current leader, but not limbo owner with elections on 5. Demoting current leader with elections on and off 6. Simultaneous promote/demote 7. Promoting voter 8. Interfering promote/demote while writing new term to wal 9. Interfering promote/demote while waiting for synchro queue to be emptied 10. Interfering promote while waiting for limbo to be acked (similar to replication/gh-5430-qsync-promote-crash.test.lua) Closes #6033 NO_DOC=testing stuff NO_CHANGELOG=testing stuff
kyukhin
pushed a commit
that referenced
this issue
Jun 30, 2022
Covered most of box_promote and box_demote with tests: 1. Promote/demote unconfigured box 2. Promoting current leader with elections on and off 3. Demoting follower with elections on and off 4. Promoting current leader, but not limbo owner with elections on 5. Demoting current leader with elections on and off 6. Simultaneous promote/demote 7. Promoting voter 8. Interfering promote/demote while writing new term to wal 9. Interfering promote/demote while waiting for synchro queue to be emptied 10. Interfering promote while waiting for limbo to be acked (similar to replication/gh-5430-qsync-promote-crash.test.lua) Closes #6033 NO_DOC=testing stuff NO_CHANGELOG=testing stuff (cherry picked from commit 5a8dca7)
mkokryashkin
pushed a commit
to mkokryashkin/tarantool
that referenced
this issue
Sep 9, 2022
Covered most of box_promote and box_demote with tests: 1. Promote/demote unconfigured box 2. Promoting current leader with elections on and off 3. Demoting follower with elections on and off 4. Promoting current leader, but not limbo owner with elections on 5. Demoting current leader with elections on and off 6. Simultaneous promote/demote 7. Promoting voter 8. Interfering promote/demote while writing new term to wal 9. Interfering promote/demote while waiting for synchro queue to be emptied 10. Interfering promote while waiting for limbo to be acked (similar to replication/tarantoolgh-5430-qsync-promote-crash.test.lua) Closes tarantool#6033 NO_DOC=testing stuff NO_CHANGELOG=testing stuff
CuriousGeorgiy
added a commit
to CuriousGeorgiy/tarantool
that referenced
this issue
Jul 24, 2024
The test blocks on the `wait_log` for registering replica2 on the master node, while the master is blocked by the WAL delay injection after replica1 is starting to get registered. The `wait_log` does not throw an error on timeout, and its return value is ignored in the test, so the test simply continued after the timeout and succeeded without the necessary synchronization due to a mere coincidence. To fix the test, let's move the `wait_log` synchronization after we unblock the master from the WAL delay injection, and echo the `wait_log` result. NO_CHANGELOG=<test fix> NO_DOC=<test fix>
CuriousGeorgiy
added a commit
to CuriousGeorgiy/tarantool
that referenced
this issue
Jul 24, 2024
The test blocks on the `wait_log` for registering replica2 on the master node, while the master is blocked by the WAL delay injection after replica1 is starting to get registered. The `wait_log` does not throw an error on timeout, and its return value is ignored in the test, so the test simply continued after the timeout and succeeded without the necessary synchronization due to a mere coincidence. To fix the test, let's move the `wait_log` synchronization after we unblock the master from the WAL delay injection, and echo the `wait_log` result. Closes tarantool#9617 NO_CHANGELOG=<test fix> NO_DOC=<test fix>
CuriousGeorgiy
added a commit
to CuriousGeorgiy/tarantool
that referenced
this issue
Jul 25, 2024
The test blocks on the `wait_log` for registering replica2 on the master node, while the master is blocked by the WAL delay injection after replica1 is starting to get registered. The `wait_log` does not throw an error on timeout, and its return value is ignored in the test, so the test simply continued after the timeout and succeeded without the necessary synchronization due to a mere coincidence. To fix the test, let's move the `wait_log` synchronization after we unblock the master from the WAL delay injection, and echo the `wait_log` result. Closes tarantool#9617 NO_CHANGELOG=<test fix> NO_DOC=<test fix>
CuriousGeorgiy
added a commit
to CuriousGeorgiy/tarantool
that referenced
this issue
Jul 31, 2024
The test blocks on the `wait_log` for registering replica2 on the master node, while the master is blocked by the WAL delay injection after replica1 is starting to get registered. The `wait_log` does not throw an error on timeout, and its return value is ignored in the test, so the test simply continued after the timeout and succeeded without the necessary synchronization due to a mere coincidence. To fix the test, let's move the `wait_log` synchronization after we unblock the master from the WAL delay injection, and echo the `wait_log` result. Closes tarantool#9617 NO_CHANGELOG=<test fix> NO_DOC=<test fix>
CuriousGeorgiy
added a commit
to CuriousGeorgiy/tarantool
that referenced
this issue
Aug 6, 2024
The test blocked on the `wait_log` for registering replica2 on the master nod. The `wait_log` does not throw an error on timeout, and its return value is ignored in the test, so the test simply continued after the timeout and succeeded. The reason the test blocked was that after 70a6883 we are unable to register an anonymous replica while its relay has not stopped: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/box.cc#L4422-L4427 At the same time, the anonymous replica's relay cannot finish, because it is blocked by `cbus_unpair` in `wal_clear_watcher`: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/relay.cc#L1068-L1074 https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/lib/core/cbus.h#L440-L442 To fix this let's move `ERRINJ_REPLICA_JOIN_DELAY` before `box_register_replica`. This error injection is not used right now, so we can reuse it here instead of `ERRINJ_WAL_DELAY`. This way the WAL won't get blocked, and we will be able to get 2 concurrent replica registrations. Let's also echo the `wait_log` result to make sure the fails in the future. Closes tarantool#9617 NO_CHANGELOG=<test fix> NO_DOC=<test fix>
CuriousGeorgiy
added a commit
to CuriousGeorgiy/tarantool
that referenced
this issue
Aug 6, 2024
The test blocked on the `wait_log` for registering replica2 on the master nod. The `wait_log` does not throw an error on timeout, and its return value is ignored in the test, so the test simply continued after the timeout and succeeded. The reason the test blocked was that after 70a6883 we are unable to register an anonymous replica while its relay has not stopped: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/box.cc#L4422-L4427 At the same time, the anonymous replica's relay cannot finish, because it is blocked by `cbus_unpair` in `wal_clear_watcher`: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/relay.cc#L1068-L1074 https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/lib/core/cbus.h#L440-L442 To fix this let's move `ERRINJ_REPLICA_JOIN_DELAY` before `box_register_replica`. This error injection is not used right now, so we can reuse it here instead of `ERRINJ_WAL_DELAY`. This way the WAL won't get blocked, and we will be able to get 2 concurrent replica registrations. Let's also echo the `wait_log` result to make sure the fails in the future. Closes tarantool#9617 NO_CHANGELOG=<test fix> NO_DOC=<test fix>
CuriousGeorgiy
added a commit
to CuriousGeorgiy/tarantool
that referenced
this issue
Aug 7, 2024
The test blocked on the `wait_log` for registering replica2 on the master node. The `wait_log` does not throw an error on timeout, and its return value is ignored in the test, so the test simply continued after the timeout and succeeded. The reason the test blocked was that after 70a6883 we are unable to register an anonymous replica while its relay has not stopped: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/box.cc#L4422-L4427 At the same time, the anonymous replica's relay cannot finish, because it is blocked by `cbus_unpair` in `wal_clear_watcher`: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/relay.cc#L1068-L1074 https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/lib/core/cbus.h#L440-L442 To fix this let's move `ERRINJ_REPLICA_JOIN_DELAY` before `box_register_replica`. This error injection is not used right now, so we can reuse it here instead of `ERRINJ_WAL_DELAY`. This way the WAL won't get blocked, and we will be able to get 2 concurrent replica registrations. Let's also echo the `wait_log` result to make sure the fails in the future. Closes tarantool#9617 NO_CHANGELOG=<test fix> NO_DOC=<test fix>
ligurio
added a commit
to ligurio/tarantool
that referenced
this issue
Aug 19, 2024
Crash the program after printing the first error report (WARNING: USE AT YOUR OWN RISK!). The flag has effect only if code was compiled with -fsanitize-recover=address compile option. ``` [061] replication/tarantoolgh-5430-cluster-mvcc.test.lua [ pass ] [050] [050] [050] [Instance "box" returns with non-zero exit code: 1] [050] [050] [test-run server "box"] Last 15 lines of the log file /tmp/t/050_box/box.log: [050] tarantool#9 0x55d6c6868851 (<unknown module>) [050] [050] Direct leak of 342 byte(s) in 5 object(s) allocated from: [050] #0 0x55d69b184cae in malloc (/__w/tarantool/tarantool/src/tarantool+0x1268cae) (BuildId: 4f3fed4334a726219fb69119e67d451f0cb1ccfa) [050] tarantool#1 0x55d69d50040c in small_asan_alloc /__w/tarantool/tarantool/src/lib/small/small/util.c:94:24 [050] tarantool#2 0x55d69d4fcb3c in smalloc /__w/tarantool/tarantool/src/lib/small/small/small_asan.c:57:5 [050] tarantool#3 0x55d69ce3782f in runtime_tuple_new /__w/tarantool/tarantool/src/box/tuple.c:138:27 [050] tarantool#4 0x55d69ce33fac in tuple_new /__w/tarantool/tarantool/src/box/tuple.h:801:9 [050] tarantool#5 0x55d69ce34844 in box_tuple_new /__w/tarantool/tarantool/src/box/tuple.c:845:22 [050] tarantool#6 0x55d69b523021 in session_settings_index_get /__w/tarantool/tarantool/src/box/session_settings.c:261:12 [050] tarantool#7 0x55d69b284077 in index_get(index*, char const*, unsigned int, tuple**) /__w/tarantool/tarantool/src/box/index.h:909:9 [050] tarantool#8 0x55d69b282794 in box_index_get /__w/tarantool/tarantool/src/box/index.cc:390:11 [050] tarantool#9 0x55d6c685ea09 (<unknown module>) [050] [050] SUMMARY: AddressSanitizer: 5627 byte(s) leaked in 83 allocation(s). [055] box-luatest/gh_8530_alter_space_snapshot_test.> [ pass ] ``` 1. https://github.com/tarantool/tarantool/actions/runs/10454868034/job/28948757147?pr=10431 2. https://github.com/google/sanitizers/wiki/AddressSanitizerFlags NO_CHANGELOG=internal NO_DOC=internal NO_TEST=internal
ligurio
added a commit
to ligurio/tarantool
that referenced
this issue
Aug 19, 2024
Crash the program after printing the first error report (WARNING: USE AT YOUR OWN RISK!). The flag has effect only if code was compiled with -fsanitize-recover=address compile option. ``` [061] replication/tarantoolgh-5430-cluster-mvcc.test.lua [ pass ] [050] [050] [050] [Instance "box" returns with non-zero exit code: 1] [050] [050] [test-run server "box"] Last 15 lines of the log file /tmp/t/050_box/box.log: [050] tarantool#9 0x55d6c6868851 (<unknown module>) [050] [050] Direct leak of 342 byte(s) in 5 object(s) allocated from: [050] #0 0x55d69b184cae in malloc (/__w/tarantool/tarantool/src/tarantool+0x1268cae) (BuildId: 4f3fed4334a726219fb69119e67d451f0cb1ccfa) [050] tarantool#1 0x55d69d50040c in small_asan_alloc /__w/tarantool/tarantool/src/lib/small/small/util.c:94:24 [050] tarantool#2 0x55d69d4fcb3c in smalloc /__w/tarantool/tarantool/src/lib/small/small/small_asan.c:57:5 [050] tarantool#3 0x55d69ce3782f in runtime_tuple_new /__w/tarantool/tarantool/src/box/tuple.c:138:27 [050] tarantool#4 0x55d69ce33fac in tuple_new /__w/tarantool/tarantool/src/box/tuple.h:801:9 [050] tarantool#5 0x55d69ce34844 in box_tuple_new /__w/tarantool/tarantool/src/box/tuple.c:845:22 [050] tarantool#6 0x55d69b523021 in session_settings_index_get /__w/tarantool/tarantool/src/box/session_settings.c:261:12 [050] tarantool#7 0x55d69b284077 in index_get(index*, char const*, unsigned int, tuple**) /__w/tarantool/tarantool/src/box/index.h:909:9 [050] tarantool#8 0x55d69b282794 in box_index_get /__w/tarantool/tarantool/src/box/index.cc:390:11 [050] tarantool#9 0x55d6c685ea09 (<unknown module>) [050] [050] SUMMARY: AddressSanitizer: 5627 byte(s) leaked in 83 allocation(s). [055] box-luatest/gh_8530_alter_space_snapshot_test.> [ pass ] ``` 1. https://github.com/tarantool/tarantool/actions/runs/10454868034/job/28948757147?pr=10431 2. https://github.com/google/sanitizers/wiki/AddressSanitizerFlags NO_CHANGELOG=internal NO_DOC=internal NO_TEST=internal
ligurio
added a commit
to ligurio/tarantool
that referenced
this issue
Aug 20, 2024
Crash the program after printing the first error report (WARNING: USE AT YOUR OWN RISK!). The flag has effect only if code was compiled with -fsanitize-recover=address compile option. ``` [061] replication/tarantoolgh-5430-cluster-mvcc.test.lua [ pass ] [050] [050] [050] [Instance "box" returns with non-zero exit code: 1] [050] [050] [test-run server "box"] Last 15 lines of the log file /tmp/t/050_box/box.log: [050] tarantool#9 0x55d6c6868851 (<unknown module>) [050] [050] Direct leak of 342 byte(s) in 5 object(s) allocated from: [050] #0 0x55d69b184cae in malloc (/__w/tarantool/tarantool/src/tarantool+0x1268cae) (BuildId: 4f3fed4334a726219fb69119e67d451f0cb1ccfa) [050] tarantool#1 0x55d69d50040c in small_asan_alloc /__w/tarantool/tarantool/src/lib/small/small/util.c:94:24 [050] tarantool#2 0x55d69d4fcb3c in smalloc /__w/tarantool/tarantool/src/lib/small/small/small_asan.c:57:5 [050] tarantool#3 0x55d69ce3782f in runtime_tuple_new /__w/tarantool/tarantool/src/box/tuple.c:138:27 [050] tarantool#4 0x55d69ce33fac in tuple_new /__w/tarantool/tarantool/src/box/tuple.h:801:9 [050] tarantool#5 0x55d69ce34844 in box_tuple_new /__w/tarantool/tarantool/src/box/tuple.c:845:22 [050] tarantool#6 0x55d69b523021 in session_settings_index_get /__w/tarantool/tarantool/src/box/session_settings.c:261:12 [050] tarantool#7 0x55d69b284077 in index_get(index*, char const*, unsigned int, tuple**) /__w/tarantool/tarantool/src/box/index.h:909:9 [050] tarantool#8 0x55d69b282794 in box_index_get /__w/tarantool/tarantool/src/box/index.cc:390:11 [050] tarantool#9 0x55d6c685ea09 (<unknown module>) [050] [050] SUMMARY: AddressSanitizer: 5627 byte(s) leaked in 83 allocation(s). [055] box-luatest/gh_8530_alter_space_snapshot_test.> [ pass ] ``` 1. https://github.com/tarantool/tarantool/actions/runs/10454868034/job/28948757147?pr=10431 2. https://github.com/google/sanitizers/wiki/AddressSanitizerFlags NO_CHANGELOG=internal NO_DOC=internal NO_TEST=internal
CuriousGeorgiy
added a commit
to CuriousGeorgiy/tarantool
that referenced
this issue
Aug 21, 2024
The test blocked on the `wait_log` for registering replica2 on the master node. The `wait_log` does not throw an error on timeout, and its return value is ignored in the test, so the test simply continued after the timeout and succeeded. The reason the test blocked was that after 70a6883 we are unable to register an anonymous replica while its relay has not stopped: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/box.cc#L4422-L4427 At the same time, the anonymous replica's relay cannot finish, because it is blocked by `cbus_unpair` in `wal_clear_watcher`: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/relay.cc#L1068-L1074 https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/lib/core/cbus.h#L440-L442 To fix this let's move `ERRINJ_REPLICA_JOIN_DELAY` before `box_register_replica`. This error injection is not used right now, so we can reuse it here instead of `ERRINJ_WAL_DELAY`. This way the WAL won't get blocked, and we will be able to get 2 concurrent replica registrations. Let's also echo the `wait_log` result to make sure the fails in the future. Closes tarantool#9617 NO_CHANGELOG=<test fix> NO_DOC=<test fix>
CuriousGeorgiy
added a commit
to CuriousGeorgiy/tarantool
that referenced
this issue
Aug 21, 2024
The test blocked on the `wait_log` for registering replica2 on the master node. The `wait_log` does not throw an error on timeout, and its return value is ignored in the test, so the test simply continued after the timeout and succeeded. The reason the test blocked was that after 70a6883 we are unable to register an anonymous replica while its relay has not stopped: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/box.cc#L4422-L4427 At the same time, the anonymous replica's relay cannot finish, because it is blocked by `cbus_unpair` in `wal_clear_watcher`: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/relay.cc#L1068-L1074 https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/lib/core/cbus.h#L440-L442 To fix this let's move `ERRINJ_REPLICA_JOIN_DELAY` before `box_register_replica`. This error injection is not used right now, so we can reuse it here instead of `ERRINJ_WAL_DELAY`. This way the WAL won't get blocked, and we will be able to get 2 concurrent replica registrations. Let's also echo the `wait_log` result to make sure the fails in the future. Closes tarantool#9617 NO_CHANGELOG=<test fix> NO_DOC=<test fix>
CuriousGeorgiy
added a commit
to CuriousGeorgiy/tarantool
that referenced
this issue
Aug 21, 2024
The test blocked on the `wait_log` for registering replica2 on the master node. The `wait_log` does not throw an error on timeout, and its return value is ignored in the test, so the test simply continued after the timeout and succeeded. The reason the test blocked was that after 70a6883 we are unable to register an anonymous replica while its relay has not stopped: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/box.cc#L4422-L4427 At the same time, the anonymous replica's relay cannot finish, because it is blocked by `cbus_unpair` in `wal_clear_watcher`: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/relay.cc#L1068-L1074 https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/lib/core/cbus.h#L440-L442 To fix this let's move `ERRINJ_REPLICA_JOIN_DELAY` before `box_register_replica`. This error injection is not used right now, so we can reuse it here instead of `ERRINJ_WAL_DELAY`. This way the WAL won't get blocked, and we will be able to get 2 concurrent replica registrations. Let's also echo the `wait_log` result to make sure the fails in the future. Closes tarantool#9617 NO_CHANGELOG=<test fix> NO_DOC=<test fix>
Gerold103
pushed a commit
that referenced
this issue
Aug 26, 2024
The test blocked on the `wait_log` for registering replica2 on the master node. The `wait_log` does not throw an error on timeout, and its return value is ignored in the test, so the test simply continued after the timeout and succeeded. The reason the test blocked was that after 70a6883 we are unable to register an anonymous replica while its relay has not stopped: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/box.cc#L4422-L4427 At the same time, the anonymous replica's relay cannot finish, because it is blocked by `cbus_unpair` in `wal_clear_watcher`: https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/box/relay.cc#L1068-L1074 https://github.com/tarantool/tarantool/blob/9e616ab6f2f94ba2bcad3044187c474a1c05a8c5/src/lib/core/cbus.h#L440-L442 To fix this let's move `ERRINJ_REPLICA_JOIN_DELAY` before `box_register_replica`. This error injection is not used right now, so we can reuse it here instead of `ERRINJ_WAL_DELAY`. This way the WAL won't get blocked, and we will be able to get 2 concurrent replica registrations. Let's also echo the `wait_log` result to make sure the fails in the future. Closes #9617 NO_CHANGELOG=<test fix> NO_DOC=<test fix>
ligurio
added a commit
to ligurio/tarantool
that referenced
this issue
Aug 30, 2024
Crash the program after printing the first error report (WARNING: USE AT YOUR OWN RISK!). The flag has effect only if code was compiled with -fsanitize-recover=address compile option. ``` [061] replication/tarantoolgh-5430-cluster-mvcc.test.lua [ pass ] [050] [050] [050] [Instance "box" returns with non-zero exit code: 1] [050] [050] [test-run server "box"] Last 15 lines of the log file /tmp/t/050_box/box.log: [050] tarantool#9 0x55d6c6868851 (<unknown module>) [050] [050] Direct leak of 342 byte(s) in 5 object(s) allocated from: [050] #0 0x55d69b184cae in malloc (/__w/tarantool/tarantool/src/tarantool+0x1268cae) (BuildId: 4f3fed4334a726219fb69119e67d451f0cb1ccfa) [050] tarantool#1 0x55d69d50040c in small_asan_alloc /__w/tarantool/tarantool/src/lib/small/small/util.c:94:24 [050] tarantool#2 0x55d69d4fcb3c in smalloc /__w/tarantool/tarantool/src/lib/small/small/small_asan.c:57:5 [050] tarantool#3 0x55d69ce3782f in runtime_tuple_new /__w/tarantool/tarantool/src/box/tuple.c:138:27 [050] tarantool#4 0x55d69ce33fac in tuple_new /__w/tarantool/tarantool/src/box/tuple.h:801:9 [050] tarantool#5 0x55d69ce34844 in box_tuple_new /__w/tarantool/tarantool/src/box/tuple.c:845:22 [050] tarantool#6 0x55d69b523021 in session_settings_index_get /__w/tarantool/tarantool/src/box/session_settings.c:261:12 [050] tarantool#7 0x55d69b284077 in index_get(index*, char const*, unsigned int, tuple**) /__w/tarantool/tarantool/src/box/index.h:909:9 [050] tarantool#8 0x55d69b282794 in box_index_get /__w/tarantool/tarantool/src/box/index.cc:390:11 [050] tarantool#9 0x55d6c685ea09 (<unknown module>) [050] [050] SUMMARY: AddressSanitizer: 5627 byte(s) leaked in 83 allocation(s). [055] box-luatest/gh_8530_alter_space_snapshot_test.> [ pass ] ``` 1. https://github.com/tarantool/tarantool/actions/runs/10454868034/job/28948757147?pr=10431 2. https://github.com/google/sanitizers/wiki/AddressSanitizerFlags NO_CHANGELOG=internal NO_DOC=internal NO_TEST=internal
ligurio
added a commit
to ligurio/tarantool
that referenced
this issue
Sep 5, 2024
Crash the program after printing the first error report (WARNING: USE AT YOUR OWN RISK!). The flag has effect only if code was compiled with -fsanitize-recover=address compile option. ``` [061] replication/tarantoolgh-5430-cluster-mvcc.test.lua [ pass ] [050] [050] [050] [Instance "box" returns with non-zero exit code: 1] [050] [050] [test-run server "box"] Last 15 lines of the log file /tmp/t/050_box/box.log: [050] tarantool#9 0x55d6c6868851 (<unknown module>) [050] [050] Direct leak of 342 byte(s) in 5 object(s) allocated from: [050] #0 0x55d69b184cae in malloc (/__w/tarantool/tarantool/src/tarantool+0x1268cae) (BuildId: 4f3fed4334a726219fb69119e67d451f0cb1ccfa) [050] tarantool#1 0x55d69d50040c in small_asan_alloc /__w/tarantool/tarantool/src/lib/small/small/util.c:94:24 [050] tarantool#2 0x55d69d4fcb3c in smalloc /__w/tarantool/tarantool/src/lib/small/small/small_asan.c:57:5 [050] tarantool#3 0x55d69ce3782f in runtime_tuple_new /__w/tarantool/tarantool/src/box/tuple.c:138:27 [050] tarantool#4 0x55d69ce33fac in tuple_new /__w/tarantool/tarantool/src/box/tuple.h:801:9 [050] tarantool#5 0x55d69ce34844 in box_tuple_new /__w/tarantool/tarantool/src/box/tuple.c:845:22 [050] tarantool#6 0x55d69b523021 in session_settings_index_get /__w/tarantool/tarantool/src/box/session_settings.c:261:12 [050] tarantool#7 0x55d69b284077 in index_get(index*, char const*, unsigned int, tuple**) /__w/tarantool/tarantool/src/box/index.h:909:9 [050] tarantool#8 0x55d69b282794 in box_index_get /__w/tarantool/tarantool/src/box/index.cc:390:11 [050] tarantool#9 0x55d6c685ea09 (<unknown module>) [050] [050] SUMMARY: AddressSanitizer: 5627 byte(s) leaked in 83 allocation(s). [055] box-luatest/gh_8530_alter_space_snapshot_test.> [ pass ] ``` 1. https://github.com/tarantool/tarantool/actions/runs/10454868034/job/28948757147?pr=10431 2. https://github.com/google/sanitizers/wiki/AddressSanitizerFlags NO_CHANGELOG=internal NO_DOC=internal NO_TEST=internal
ligurio
added a commit
to ligurio/tarantool
that referenced
this issue
Sep 5, 2024
Crash the program after printing the first error report (WARNING: USE AT YOUR OWN RISK!). The flag has effect only if code was compiled with -fsanitize-recover=address compile option. ``` [061] replication/tarantoolgh-5430-cluster-mvcc.test.lua [ pass ] [050] [050] [050] [Instance "box" returns with non-zero exit code: 1] [050] [050] [test-run server "box"] Last 15 lines of the log file /tmp/t/050_box/box.log: [050] tarantool#9 0x55d6c6868851 (<unknown module>) [050] [050] Direct leak of 342 byte(s) in 5 object(s) allocated from: [050] #0 0x55d69b184cae in malloc (/__w/tarantool/tarantool/src/tarantool+0x1268cae) (BuildId: 4f3fed4334a726219fb69119e67d451f0cb1ccfa) [050] tarantool#1 0x55d69d50040c in small_asan_alloc /__w/tarantool/tarantool/src/lib/small/small/util.c:94:24 [050] tarantool#2 0x55d69d4fcb3c in smalloc /__w/tarantool/tarantool/src/lib/small/small/small_asan.c:57:5 [050] tarantool#3 0x55d69ce3782f in runtime_tuple_new /__w/tarantool/tarantool/src/box/tuple.c:138:27 [050] tarantool#4 0x55d69ce33fac in tuple_new /__w/tarantool/tarantool/src/box/tuple.h:801:9 [050] tarantool#5 0x55d69ce34844 in box_tuple_new /__w/tarantool/tarantool/src/box/tuple.c:845:22 [050] tarantool#6 0x55d69b523021 in session_settings_index_get /__w/tarantool/tarantool/src/box/session_settings.c:261:12 [050] tarantool#7 0x55d69b284077 in index_get(index*, char const*, unsigned int, tuple**) /__w/tarantool/tarantool/src/box/index.h:909:9 [050] tarantool#8 0x55d69b282794 in box_index_get /__w/tarantool/tarantool/src/box/index.cc:390:11 [050] tarantool#9 0x55d6c685ea09 (<unknown module>) [050] [050] SUMMARY: AddressSanitizer: 5627 byte(s) leaked in 83 allocation(s). [055] box-luatest/gh_8530_alter_space_snapshot_test.> [ pass ] ``` 1. https://github.com/tarantool/tarantool/actions/runs/10454868034/job/28948757147?pr=10431 2. https://github.com/google/sanitizers/wiki/AddressSanitizerFlags NO_CHANGELOG=internal NO_DOC=internal NO_TEST=internal
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Tarantool version:
Tarantool 2.6.0-208-ga20a04cba
Target: FreeBSD-amd64-RelWithDebInfo
Build options: cmake . -DCMAKE_INSTALL_PREFIX=/usr/local -DENABLE_BACKTRACE=OFF
Compiler: /usr/bin/cc /usr/bin/c++
C_FLAGS: -Wno-unknown-pragmas -fexceptions -funwind-tables -fno-common -std=c11 -Wall -Wextra -Wno-strict-aliasing -Wno-char-subscripts -Wno-gnu-alignof-expression -Werror
CXX_FLAGS: -Wno-unknown-pragmas -fexceptions -funwind-tables -fno-common -std=c++11 -Wall -Wextra -Wno-strict-aliasing -Wno-char-subscripts -Wno-invalid-offsetof -Wno-gnu-alignof-expression -Werror
OS version:
FreeBSD 12
Bug description:
artifacts.zip
results file checksum: afaa5d0f392c8de5420a05b268d04741
results file checksum: 1c68d778b6e78dff37609b55d536cfd8
[001] Assertion failed: (lsn > prev_lsn), function vclock_follow, file /home/vagrant/tarantool/src/lib/vclock/vclock.c, line 46.
Main log:
Steps to reproduce:
To reproduce errors 2, 3, 4 just run single test in loop on FreeBSD VMware with command:
Optional (but very desirable):
The text was updated successfully, but these errors were encountered: