Test runs inconsistent?

[verdverm]

I think I've been seeing issues in the test environment, both locally and on travis. (see builds for #235 #236)

• npm test fails and then passes on a second attempt.
• npm test passes and npm run coverage fails

Is this a known issue? Any thoughts on the causes?

(I see test and coverage use different networks and binaries for the test network)

Maybe the difference between test and coverage is also due to branches? I've noticed that coverage is not picking up the changed files. (See 235 on travis)

[sohkai]

The coverage failure in #236 seems to be a sol-cover issue; it seems to not be using a .call() on that test.

What does npm test fail on?

[verdverm]

I think the KernelUpgrade section? I'll make note to give a more certain response next time I see it.

[sohkai]

Closing, since this seems to not be reproducible. Our testing set up has also changed significantly since this was issued.

Please open again if it's consistent :).