This repository was archived by the owner on Oct 28, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
This repository was archived by the owner on Oct 28, 2021. It is now read-only.
testeth help output has weird indentation #5626
Copy link
Copy link
Closed
Labels
Description
Minor issue with formatting, I have no idea why it happens:
>test/testeth -- --help
Usage:
Setting test suite
-t <TestSuite> Execute test operations
-t <TestSuite>/<TestCase>
--testpath <PathToTheTestRepo>
Debugging
-d <index> Set the transaction data array index when running GeneralStateTests
-g <index> Set the transaction gas array index when running GeneralStateTests
-v <index> Set the transaction value array index when running GeneralStateTests
--singletest <TestName> Run on a single test
--singletest <TestFile> <TestName>
--singlenet <networkId> Run tests for a specific network (Frontier|Homestead|EIP150|EIP158|Byzantium|Constantinople|ConstantinopleFix)
--verbosity <level> Set logs verbosity. 0 - silent, 1 - only errors, 2 - informative, >2 - detailed
--vm <name|path> (=legacy) Set VM type for VMTests suite. Available options are: interpreter, legacy.
--evmc <option>=<value> EVMC option
--vmtrace Enable VM trace for the test. (Require build with VMTRACE=1)
--jsontrace <Options> Enable VM trace to stdout in json format. Argument is a json config: '{ "disableStorage" : false, "disableMemory" : false, "disableStack" : false, "fullStorage" : true }'
--stats <OutFile> Output debug stats to the file
--exectimelog Output execution time for each test suite
--statediff Trace state difference for state tests
Additional Tests
--all Enable all tests
Test Generation
--filltests Run test fillers
--fillchain When filling the state tests, fill tests as blockchain instead
--showhash Show filler hash debug information
--randomcode <MaxOpcodeNum> Generate smart random EVM code
--createRandomTest Create random test and output it to the console
--createRandomTest <PathToOptions.json>Use following options file for random code generation
--seed <uint> Define a seed for random test
--options <PathTo.json> Use following options file for random code generation
--db <name> (=memorydb) Use the supplied database for the block and state databases. Valid options: leveldb, rocksdb, memorydb
--help Display list of command arguments
--version Display build information
Some lines like --vmtrace or --fillchain are indented, but they shouldn't be.
Reactions are currently unavailable