You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Python produces ton of output
is there a way to disable it and control the output. to have only what we want to read
since there test vector names are so huge I have this suggestion.
when designing post state in test
if create2_dest_already_in_state:
# The create2 collision causes all the code to go out of gas and return 0x00
post[address_to] = Account(
storage={code_worked: 0x01, first_create2_result: 0x00, second_create2_result: 0x00}
)
post[address_create2_storage] = Account(storage={create2_constructor_worked: 0x00})
if call_create2_contract_in_between:
make a debug function
if create2_dest_already_in_state:
POSTSTATE()
if such function called in the test. it will tell to disable all python log. and print only the post state of produced test vector.
by
state_test(pre,txs...)
after it printed poststate, all the rest, following state_test(pre,txs...) calls are ignored
The text was updated successfully, but these errors were encountered:
Python produces ton of output
is there a way to disable it and control the output. to have only what we want to read
since there test vector names are so huge I have this suggestion.
when designing post state in test
make a debug function
if such function called in the test. it will tell to disable all python log. and print only the post state of produced test vector.
by
after it printed poststate, all the rest, following
state_test(pre,txs...)
calls are ignoredThe text was updated successfully, but these errors were encountered: