Build failure: history.c '!!mesage_exists' should be TRUE

I have just wittnessed a build test failure on salsa CI:

https://salsa.debian.org/DebianOnMobile-team/chatty/-/jobs/872739#L2551

2536 5/6 history                 FAIL           0.07s (killed by signal 6 SIGABRT)
2537 --- command ---
2538 22:36:48 G_TEST_SRCDIR='/tmp/reprotest.m3kDyw/const_build_path/const_build_path/tests' MALLOC_CHECK_='2' G_TEST_BUILDDIR='/tmp/reprotest.m3kDyw/const_build_path/const_build_path/_build/tests' GSETTINGS_SCHEMA_DIR='/tmp/reprotest.m3kDyw/const_build_path/const_build_path/_build/data' /tmp/reprotest.m3kDyw/const_build_path/const_build_path/_build/tests/history
2539 --- stdout ---
2540 # random seed: R02S3d650dceb659356375f098bacb6577ed
2541 1..3
2542 # Start of history tests
2543 # chatty-history-DEBUG: Database opened successfully
2544 # chatty-history-DEBUG: chatty_chat table created successfully
2545 # chatty-history-DEBUG: Create Index chatty_chat_accuid: OK
2546 # chatty-history-DEBUG: chatty_im table created successfully
2547 # chatty-history-DEBUG: Create Index chatty_im_accuid: OK
2548 Bail out! ERROR:../tests/history.c:183:add_im: '!!message_exists' should be TRUE
2549 --- stderr ---
2550 **
2551 ERROR:../tests/history.c:183:add_im: '!!message_exists' should be TRUE
2552 -------

I have come across the same failure recently (I think it was in a local build - so I don't think it has anything to do with reprotest) and "fixed" it by rerunning the build.

Rerunning the failed job also "fixed" it: https://salsa.debian.org/DebianOnMobile-team/chatty/-/jobs/872811