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 state.FilesystemAttachmentInfo = state.FilesystemAttachmentInfo{MountPoint:"", ReadOnly:true} ... expected state.FilesystemAttachmentInfo = state.FilesystemAttachmentInfo{MountPoint:"", ReadOnly:true} ... mismatch at .ReadOnly: unequal; obtained true; expected true um... wat? from state/filesystem.go: type FilesystemAttachmentInfo struct { // MountPoint is the path at which the filesystem is mounted on the // machine. MountPoint may be empty, meaning that the filesystem is // not mounted yet. MountPoint string `bson:"mountpoint"` ReadOnly bool `bson:"read-only"` } So we have a plain struct with a string and a bool. How can jc.DeepEquals fail with this? Confusedly yours, Tim -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
