a5cec358a9
I am not 100% percent sure what is happening but it seems that newMessageFilter is async operation, result of this operation is assumed to be used in callbacks. All other tests are doing at least 1 io operation in between creating a filter and posting a message, and it must be enough for newMessageFilter to complete. Setting higher GOMAXPROCS allows Otto vm to execute received io requests immediatly. While lower number of processes may result in events re-ordering. https://github.com/ethereum/web3.js/blob/develop/lib/web3/methods/shh.js#L39-L41 I tested this change with GOMAXPROCS=1 and it passes consistently. |
||
|---|---|---|
| .. | ||
| destructive | ||
| e2e | ||
| utils | ||