diff options
| author | moneromooo-monero <moneromooo-monero@users.noreply.github.com> | 2017-02-14 18:55:01 +0000 |
|---|---|---|
| committer | moneromooo-monero <moneromooo-monero@users.noreply.github.com> | 2017-02-14 18:56:42 +0000 |
| commit | b6a2230e6f6253426276cad577dc5dd8f192d139 (patch) | |
| tree | c4f0d0cd5390470d672c7379ad549b6f2c2d7238 /tests | |
| parent | hardfork: tone down some logs (diff) | |
| download | monero-b6a2230e6f6253426276cad577dc5dd8f192d139.tar.xz | |
unit_tests: fix minor blockchain_db regression
Due to the change in ordering for adding block and tx data
to the database in f2986ccfc1f41023cd667dbb488a10df492eb8e7,
adding a block twice now throws TX_EXISTS, not BLOCK_EXISTS.
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/unit_tests/blockchain_db.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/unit_tests/blockchain_db.cpp b/tests/unit_tests/blockchain_db.cpp index 8fc10be10..faf4c776f 100644 --- a/tests/unit_tests/blockchain_db.cpp +++ b/tests/unit_tests/blockchain_db.cpp @@ -288,7 +288,7 @@ TYPED_TEST(BlockchainDBTest, AddBlock) ASSERT_TRUE(compare_blocks(this->m_blocks[0], b)); // assert that we can't add the same block twice - ASSERT_THROW(this->m_db->add_block(this->m_blocks[0], t_sizes[0], t_diffs[0], t_coins[0], this->m_txs[0]), BLOCK_EXISTS); + ASSERT_THROW(this->m_db->add_block(this->m_blocks[0], t_sizes[0], t_diffs[0], t_coins[0], this->m_txs[0]), TX_EXISTS); for (auto& h : this->m_blocks[0].tx_hashes) { |