aboutsummaryrefslogtreecommitdiff
path: root/tests/core_tests/chaingen.h (follow)
AgeCommit message (Collapse)AuthorFilesLines
2018-07-07core_tests: add --filter to select which tests to runmoneromooo-monero1-0/+1
2018-06-26replace std::list with std::vector on some hot pathsmoneromooo-monero1-1/+1
also use reserve where appropriate
2018-01-26Update 2018 copyrightxmr-eric1-1/+1
2017-12-17Match surae's recommendation to derive multisig keysmoneromooo-monero1-4/+6
2017-12-17add multisig core test and factor multisig building blocksmoneromooo-monero1-0/+48
2017-12-16cryptonote_core does not depend on p2p anymoremoneromooo-monero1-1/+1
As a followon side effect, this makes a lot of inline code included only in particular cpp files (and instanciated when necessary.
2017-06-09core_tests: fix tests failing due to new txpool code requitring batch ↵moneromooo-monero1-0/+1
transactions
2017-05-25Move txpool to the databasemoneromooo-monero1-0/+10
Integration could go further (ie, return_tx_to_pool calls should not be needed anymore, possibly other things). poolstate.bin is now obsolete.
2017-02-21update copyright year, fix occasional lack of newline at line endRiccardo Spagni1-1/+1
2017-02-08extract some basic code from libcryptonote_core into libcryptonote_basickenshi841-5/+5
2017-01-16Change logging to easylogging++moneromooo-monero1-50/+13
This replaces the epee and data_loggers logging systems with a single one, and also adds filename:line and explicit severity levels. Categories may be defined, and logging severity set by category (or set of categories). epee style 0-4 log level maps to a sensible severity configuration. Log files now also rotate when reaching 100 MB. To select which logs to output, use the MONERO_LOGS environment variable, with a comma separated list of categories (globs are supported), with their requested severity level after a colon. If a log matches more than one such setting, the last one in the configuration string applies. A few examples: This one is (mostly) silent, only outputting fatal errors: MONERO_LOGS=*:FATAL This one is very verbose: MONERO_LOGS=*:TRACE This one is totally silent (logwise): MONERO_LOGS="" This one outputs all errors and warnings, except for the "verify" category, which prints just fatal errors (the verify category is used for logs about incoming transactions and blocks, and it is expected that some/many will fail to verify, hence we don't want the spam): MONERO_LOGS=*:WARNING,verify:FATAL Log levels are, in decreasing order of priority: FATAL, ERROR, WARNING, INFO, DEBUG, TRACE Subcategories may be added using prefixes and globs. This example will output net.p2p logs at the TRACE level, but all other net* logs only at INFO: MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE Logs which are intended for the user (which Monero was using a lot through epee, but really isn't a nice way to go things) should use the "global" category. There are a few helper macros for using this category, eg: MGINFO("this shows up by default") or MGINFO_RED("this is red"), to try to keep a similar look and feel for now. Existing epee log macros still exist, and map to the new log levels, but since they're used as a "user facing" UI element as much as a logging system, they often don't map well to log severities (ie, a log level 0 log may be an error, or may be something we want the user to see, such as an important info). In those cases, I tried to use the new macros. In other cases, I left the existing macros in. When modifying logs, it is probably best to switch to the new macros with explicit levels. The --log-level options and set_log commands now also accept category settings, in addition to the epee style log levels.
2017-01-14fix do_not_relay not preventing relaying on a timermoneromooo-monero1-2/+2
Also print its value when printing pool
2016-08-28tests: hard fork list must end with a 0moneromooo-monero1-2/+2
2016-08-28Add rct core testsmoneromooo-monero1-3/+6
2016-05-01tests: fix tests broken by the removal of the block reward accumulation loopmoneromooo-monero1-1/+1
The tests for rejection of unmixable outputs in v2 are commented out, as there are no unmixable outputs created anymore. This should be restored at some point.
2016-04-02tests: fix build with older GCCJavier Smooth1-2/+4
2016-03-21core_tests: fix compile failure with GCC 4.8.4moneromooo-monero1-1/+1
Reported and tested by smooth
2016-03-21Revert "Print stack trace upon exceptions"moneromooo-monero1-3/+3
Ain't nobody got time for link/cmake skullduggery. This reverts commit fff238ec94ac6d45fc18c315d7bc590ddfaad63d.
2016-03-19Print stack trace upon exceptionsmoneromooo-monero1-3/+3
Useful for debugging users' logs
2016-02-13core_tests: fix a compile problem with CLANGmoneromooo-monero1-1/+1
It doesn't like const objects from classes that do not have a user defined ctor, apparently. Reported by othe.
2016-02-08core_tests: add tests for hard fork behaviors (MRL-0004)moneromooo-monero1-5/+10
We also replace the --fakechain option with an optional structure containing details about configuration for the core/blockchain, for test purposes. This seems more future friendly.
2016-02-08core_tests: allow setting miner tx max_outs when creating a blockmoneromooo-monero1-2/+3
2015-12-31updated copyright yearRiccardo Spagni1-1/+1
2015-12-30core_tests: deinit core before destroying itmoneromooo-monero1-1/+3
This fixes a use after free by ioservice threads
2015-12-13core_tests: bump default test fee to 0.02 moneromoneromooo-monero1-1/+1
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.
2015-12-13add a --fakechain argument for testsmoneromooo-monero1-0/+4
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.
2015-12-09tests: remove data-dir argument registrationmoneromooo-monero1-1/+0
It is already registered in cryptonote::core::init_options, which we now call
2015-11-21Relay transactions when they linger too long in the poolmoneromooo-monero1-2/+2
The last relayed time of a transaction is maintained, and transactions will be relayed again if they are still in the pool after a certain amount of time, which increases with the transaction's age. All such transactions are resent, whether or not they originated on the local node.
2015-03-01Fix tests building -- function signatures changedThomas Winget1-1/+3
2015-01-02year updated in licenseRiccardo Spagni1-1/+1
2014-09-15Add testnet flagZachary Michaels1-1/+1
Source: cryptonotefoundation
2014-07-23License updated to BSD 3-clausefluffypony1-3/+29
2014-03-03moved all stuff to githubAntonio Juarez1-0/+646
generated by cgit v1.2.3 (git 2.25.1) at 2025-03-21 02:11:54 +0000