Don't block forever in find-new-repl-db / handle out-of-order physreps gracefully #4727
Conversation
There was a problem hiding this comment.
Coding style check: Error. ⚠.
Smoke testing: Success ✓.
Cbuild submission: Success ✓.
Regression testing: 3/557 tests failed ⚠.
The first 10 failing tests are:
writes_remsql_fdbpush_generated [setup failure]
tunables
truncatesc_offline_generated
markhannum
force-pushed
the
physrep_incoherent_8
branch
3 times, most recently
from
2c0cdf8
to
307350e
Compare
There was a problem hiding this comment.
Coding style check: Error. ⚠.
Smoke testing: Success ✓.
Cbuild submission: Success ✓.
Regression testing: 5/557 tests failed ⚠.
The first 10 failing tests are:
lostwrite [setup failure]
blkseq_race [setup failure]
sc_dups_logicalsc_generated [setup failure]
sc_remsql [setup failure]
truncatesc_offline_generated
markhannum
force-pushed
the
physrep_incoherent_8
branch
from
307350e
to
1abae56
Compare
There was a problem hiding this comment.
Coding style check: Error. ⚠.
Smoke testing: Success ✓.
Cbuild submission: Success ✓.
Regression testing: 2/557 tests failed ⚠.
The first 10 failing tests are:
lostwrite
truncatesc_offline_generated
markhannum
force-pushed
the
physrep_incoherent_8
branch
2 times, most recently
from
afca9bb
to
2e0c0c6
Compare
There was a problem hiding this comment.
Coding style check: Error. ⚠.
Smoke testing: Success ✓.
Cbuild submission: Success ✓.
Regression testing: 3/557 tests failed ⚠.
The first 10 failing tests are:
vutf8_rowlocks_off_osql_odh_blob_generated [setup failure]
sc_timepart
truncatesc_offline_generated
markhannum
force-pushed
the
physrep_incoherent_8
branch
from
2e0c0c6
to
0f8098e
Compare
There was a problem hiding this comment.
Coding style check: Error. ⚠.
Smoke testing: Success ✓.
Cbuild submission: Success ✓.
Regression testing: 1/557 tests failed ⚠.
The first 10 failing tests are:
truncatesc_offline_generated
There was a problem hiding this comment.
Coding style check: Error. ⚠.
Smoke testing: Success ✓.
Cbuild submission: Success ✓.
Regression testing: 2/558 tests failed ⚠.
The first 10 failing tests are:
mismatch_class_remsql_fdbpush_generated [setup failure]
truncatesc_offline_generated
There was a problem hiding this comment.
Coding style check: Error. ⚠.
Smoke testing: Success ✓.
Cbuild submission: Error ⚠.
Regression testing: 5/558 tests failed ⚠.
The first 10 failing tests are:
sc_dups_logicalsc_generated [setup failure]
logfill_logput_window_generated
union_parallel
truncatesc_offline_generated
dbcreate
There was a problem hiding this comment.
Coding style check: Error. ⚠.
Smoke testing: Success ✓.
Cbuild submission: Success ✓.
Regression testing: 1/558 tests failed ⚠.
The first 10 failing tests are:
truncatesc_offline_generated
Handle out-of-order on physreps gracefully Re-verify reverse-connection Signed-off-by: Mark Hannum <[email protected]>
markhannum
force-pushed
the
physrep_incoherent_8
branch
from
0f8098e
to
a69f6ea
Compare
There was a problem hiding this comment.
Coding style check: Error. ⚠.
Smoke testing: Success ✓.
Cbuild submission: Success ✓.
Regression testing: 5/558 tests failed ⚠.
The first 10 failing tests are:
sc_inserts_logicalsc_generated [setup failure]
sc_remsql_fdbpushredirect_generated [setup failure]
sc_truncate
analyze_fastinit_race
truncatesc_offline_generated
There was a problem hiding this comment.
Coding style check: Error. ⚠.
Smoke testing: Success ✓.
Cbuild submission: Success ✓.
Regression testing: 5/558 tests failed ⚠.
The first 10 failing tests are:
vutf8_rowlocks [setup failure]
lostwrite
sc_downgrade
truncatesc_offline_generated
dbcreate
This PR also introduces 'incoherent_test' under phys_rep_tiered which attempts to reproduce these situations. This is the 8.0 version of #4726