Open mdwhatcott opened 9 years ago
Here are my results for goconvey/convey tests
➜ convey git:(master) go version
go version go1.5.1 darwin/amd64
➜ convey git:(master) git branch
* master
➜ convey git:(master) go test
PASS
ok github.com/smartystreets/goconvey/convey 0.030s
So I would change title of this ticket if you mean another tests.
Here's the package with the failing tests:
go test -v github.com/smartystreets/goconvey/web/server/watch
I'm also seeing this issue, with "github.com/smartystreets/goconvey/web/server/watch/integration_test.go", but i'm consistently getting five failed assertions.
--- PASS: TestSum (0.00s)
=== RUN TestWatcher
Subject: Watcher operations
Initial scan results ✘
Manual execution produces additional results ✘
Ignore and Reinstate commands are not reflected in the scan results ✘
Adjusting the root changes the number of folders in the scanned results ✘
A bogus command does not cause any additional scanning beyond the initial scan ✔
Scanning occurs as a result of a file system update ✔
Scanning does not occur as a result of resuming after a pause ✔
Scanning should not occur when the watcher is paused ✘
Failures:
* /tmp/golang/src/github.com/smartystreets/goconvey/web/server/watch/integration_test.go
Line 81:
Expected: '1'
Actual: '0'
(Should be equal)
* /tmp/golang/src/github.com/smartystreets/goconvey/web/server/watch/integration_test.go
Line 95:
Expected: '2'
Actual: '1'
(Should be equal)
* /tmp/golang/src/github.com/smartystreets/goconvey/web/server/watch/integration_test.go
Line 112:
Expected: '1'
Actual: '0'
(Should be equal)
* /tmp/golang/src/github.com/smartystreets/goconvey/web/server/watch/integration_test.go
Line 128:
Expected: '3'
Actual: '2'
(Should be equal)
* /tmp/golang/src/github.com/smartystreets/goconvey/web/server/watch/integration_test.go
Line 196:
Expected: '2'
Actual: '1'
(Should be equal)
This should actually be resolved with this pull request:
smartystreets/goconvey: Pull Request #317
We'll just have to see when 1.5 ships.
This group of tests fail randomly (I consistently get at least one failure).
Possible problems looming:
msteinert commented