Is it possible the data is accidentally mutable and being updated
asynchronously? Such that at the time the initial comparison is made the
value is actually false, but by the time we notice the mismatch and report
on it the data has been updated and they are now the same? Bad test to
share mutable
This morning I noticed a Curse on the jes-cli branch, which included
this one on ppc64el:
http://reports.vapour.ws/releases/2855/job/run-unit-tests-trusty-ppc64el/attempt/3487
Upon looking I saw this:
storage_test.go:147:
c.Assert(info, jc.DeepEquals, expect)
... obtained
