monzero-core.git/tests/core_tests, branch v0.9.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.9.02015-12-31T06:39:56Zupdated copyright year2015-12-31T06:39:56ZRiccardo Spagniric@spagni.net2015-12-31T06:39:56Zurn:sha1:de0392685063d93dbdad3a6b1a2712eaf94dd51acore_tests: deinit core before destroying it2015-12-30T16:05:52Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-30T16:05:52Zurn:sha1:b2452151931ffe98337181567aaf797c1f530c3f
This fixes a use after free by ioservice threads
tests: fix various tests by using parameters better suited to monero2015-12-25T22:26:34Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:26:34Zurn:sha1:79beed221d9b3842b652587b5eaeed17423bd9de
Either smaller coin values (as monero has smaller block rewards),
or pre-hard fork values (full reward zone), or post-Bytecoin values
(emission speed).
tests: fix some double spending tests2015-12-25T22:23:36Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:23:36Zurn:sha1:d0a8362b6bceeb9f99ee29360c84ce49db9904d1
Some tests assume the first output in a transaction goes to the recipient.
However, it can be the change. When it is, the recipient's keys will not
recognize this output. To fix this, we send all we have, to ensure there
is no change, and the first output goes to the recipient.
I'm not sure why this worked with Cryptonote. The tests sent 17 coins,
which seems way smaller than the first Bytecoin block reward, so there
would have been change too. Maybe outputs were not shuffled originally.
tests: use 255 as a "too high" block version2015-12-25T22:22:12Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:22:12Zurn:sha1:2358d0d5be34f8dca0c14f94979300ed49e3f29f
While the original cryptonote accepted only the current major
version, we can accept higher ones.
blockchain: fix bitflipping test with quantized block rewards2015-12-25T22:07:58Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:07:58Zurn:sha1:81cb0fcdccf08afd6f37d21ccfefb31131fd3950
Block reward may now be less than the full amount allowed.
This was breaking the bitflipping test.
We now keep track of whether a block which was accepted by the core
has a lower than allowed block reward, and allow this in the test.
core_tests: fix ring_signature_1 tests2015-12-13T13:58:13Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-13T13:58:13Zurn:sha1:cbded439f45c5867e76758825f70284daca2eb47
They were trying to send too much monero, and thus failing.
The parameters were set in such a way that the (simple) output
gathering code could fulfill them for 4 block rewards for the
original Bytecoin emission, but that does not work with monero
so we need to use smaller values.
core_tests: bump default test fee to 0.02 monero2015-12-13T13:56:15Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-13T13:56:15Zurn:sha1:c3d208fcbe7d32d2764a3cb8fae5653ae5de0f49
The current monero consensus uses 0.01 per kB fees, so use enough
for 2 kB transactions for now. It'll probably have to be either
bumped further or changed to calculate the proper fee.
add a --fakechain argument for tests2015-12-13T11:38:37Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-13T11:38:37Zurn:sha1:10da0a0b7cc70fad0ffde60bdd04926484fb043a
The core tests use the blockchain, and reset it to be able
to add test data to it. This does not play nice with the
databases, since those will save that data without an explicit
save call.
We add a fakechain flag that the tests will set, which tells
the core and blockchain code to use a separate database, as
well as skip a few things like checkpoints and fixup, which
only make sense for real data.
tests: remove data-dir argument registration2015-12-09T17:31:15Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-09T17:30:30Zurn:sha1:f141869cac2c099da0e121c4723951d4ac7c36f6
It is already registered in cryptonote::core::init_options,
which we now call