Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RegTest failed when running against omnicore-qt v0.12.0 #1280

Open
msgilligan opened this issue Nov 11, 2022 · 1 comment
Open

RegTest failed when running against omnicore-qt v0.12.0 #1280

msgilligan opened this issue Nov 11, 2022 · 1 comment

Comments

@msgilligan
Copy link
Member

I was running OmniJ RegTests in an Ubuntu 11 ARM64 VM against the Qt version of Omni Core 0.12.0 as follows:

./bin/omnicore-qt -printtoconsole \
  -debug=1 \
  -regtest=1 \
  -txindex=1 \
  -experimental-btc-balances=1 \
  -peerbloomfilters \
  -omnialertallowsender=any \
  -omniactivationallowsender=any \
  -addresstype=legacy \
  -acceptnonstdtxn=1 \
  -limitancestorcount=750 \
  -limitdescendantcount=750 \
  -paytxfee=0.0001 \
  -minrelaytxfee=0.00001 \
  -listenonion=false \
  -zmqpubrawblock=tcp://0.0.0.0:38443 \
  -zmqpubhashblock=tcp://0.0.0.0:38443 \
  -zmqpubrawtx=tcp://0.0.0.0:38444 \
  -zmqpubhashtx=tcp://0.0.0.0:38444 \
  -rpcallowip=172.17.0.0/16 \
  -rpcbind=0.0.0.0 \
  -rpcuser=bitcoinrpc \
  -rpcpassword=pass

And running tests with:

cd OmniJ ; ./gradlew regTest

Expected behavior

All tests pass

Actual behavior

MetaDexSpec.One Side of the trade must be either OMNI or TOMNI fails with message Error with selected inputs for the send transaction.

To reproduce

See above.

System information

Omni Core 0.12.0 -- official Linux ARM64 build.

QEMU ARM64 virtual machine on macOS. Debian 11 with the default desktop environment.

I believe it is GUI-related -- likely because the GUI event notifications are struggling to keep up with the rapid rate of transactions and blocks generated by the regTest tests. One of the attached screenshots shows how the Qt environment is lagging behind, the others show the test results.

Screen Shot 2022-11-10 at 5 27 45 PM

Screen Shot 2022-11-10 at 5 43 29 PM

Screen Shot 2022-11-10 at 5 43 53 PM

@dexX7
Copy link
Member

dexX7 commented Nov 22, 2022

Hi @msgilligan, for some reason this happens sometimes. Can you re-run the tests?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants