--chain=dev doesn't seal when transactions are sent in parallel

[tomusdrw]

Possible workaround is to use --reaseal-min-period, but probably we should just check if there is anything in the queue after the block is mined to trigger sealing again.

[slothbag]

Just stumbled upon this same issue. I have a bunch of contract tests using mocha which submit multiple transactions in rapid succession. I have to force it to wait 2 seconds between each tx which is frustrating.

I agree with checking for pending tx's and then seal again.

[keorn]

That would be against --reseal-min-period (in Ethash you do not want to seal again even if there are more transactions). This option is also a problem with other async Engines that can create blocks more often than every 2 seconds.
It would be best if this would be Ethash specific option rather than something global: ignore otherwise like --engine-signer?

[awgneo]

@slothbag Have you successfully removed your delay in between transactions for unit tests? I too am using mocha and I have to have a delay or parity cannot take the test load, causing the time to fall behind in solidity and generally, intermittent transaction failures.

[keorn]

Use --config dev instead of --chain dev then you will get a bunch of other presets that make it work out of the box.

[awgneo]

I am using a custom chain configuration as I need to populate a bunch of accounts with ether for my tests to function. Additionally, I need my owner config file for other customizations. Finally, even that I still experience this issue.

[awgneo]

Oh, and using 1.8.2z

[awgneo]

*/z