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

Tests fail on real network. #25

Closed
SurfingNerd opened this issue Sep 16, 2020 · 2 comments
Closed

Tests fail on real network. #25

SurfingNerd opened this issue Sep 16, 2020 · 2 comments

Comments

@SurfingNerd
Copy link
Collaborator

After executing the tests against a real network,
like https://github.com/DMDcoin/honey-badger-testing/tree/35891e64bcef01cdd80cbf4e732b1120332c2220/testNode
a lot of tests that succeed in ganache, but fail in the real network.
Those that fail are all "expected promise to be rejected with an error including" tests.

Truffle sees the transaction as success in this case, but the status is false.
There is no log or logBloom involved that give more hints.

Failed Transactions and Transaction Receipt.

{{ blockHash:
   '0x782deba62ae6a27d22ad59ea3673e9fca06547d509277e56069a65462c838c11',
  blockNumber: 108,
  chainId: null,
  condition: null,
  creates: null,
  from: '0x810098c4632A8dB0160b7559ef9D64532898e0A9',
  gas: 8000000,
  gasPrice: '20000000000',
  hash:
   '0xd79bedb5d1ea769b7a86f887e218b82beaa866fac6603a75c25e5c020f51b337',
  input:
   '0x56e4d6c2000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000',
  nonce: 1,
  publicKey:
   '0x2aed4712e13175bbed2eb1ffc6111181b00bc162ce8d282549d26460628710352995fee0863ee66ddab35c29652ec4ae6eb698fffb02cdaa01e23c2929c34060',
  r:
   '0x56210735c6035f1657b7ed7951c25412ca1ffc219e89c7f3e77c9b37e55afb11',
  raw:
   '0xf90132018504a817c800837a1200948a8db1d6da9df1bdffe118063347813ddebf929d880de0b6b3a7640000b8c456e4d6c20000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000040000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001ba056210735c6035f1657b7ed7951c25412ca1ffc219e89c7f3e77c9b37e55afb11a028c986be271b1163d5125ab8a4c7f62ca559e1c789d877e6fac506648f4fa38a',
  s:
   '0x28c986be271b1163d5125ab8a4c7f62ca559e1c789d877e6fac506648f4fa38a',
  standardV: '0x0',
  to: '0x8A8Db1d6DA9DF1bdFfE118063347813DDebf929D',
  transactionIndex: 0,
  v: '0x1b',
  value: '1000000000000000000' }
{ blockHash:
   '0x782deba62ae6a27d22ad59ea3673e9fca06547d509277e56069a65462c838c11',
  blockNumber: 108,
  contractAddress: null,
  cumulativeGasUsed: 27726,
  from: '0x810098c4632a8db0160b7559ef9d64532898e0a9',
  gasUsed: 27726,
  logs: [],
  logsBloom:
   '0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000',
  status: false,
  to: '0x8a8db1d6da9df1bdffe118063347813ddebf929d',
  transactionHash:
   '0xd79bedb5d1ea769b7a86f887e218b82beaa866fac6603a75c25e5c020f51b337',
  transactionIndex: 0 }
@SurfingNerd
Copy link
Collaborator Author

@SurfingNerd
Copy link
Collaborator Author

the problem was that returning the error message was never implemented on parity/openethereum. https://github.com/openethereum/openethereum/issues/8068
This makes it very questionable if error message make sense at all, since they are ignored by the network - developing then are just bload that could just be a comment. Q: IF openethereum ignores error message anyway, is the code for execution free from this bloadware ?

SurfingNerd added a commit that referenced this issue Sep 19, 2020
…oubles. it was used for testing on a real network, but testing on real network is not possible. see #25
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

1 participant