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.