Activity log for bug #1501398

Date Who What changed Old value New value Message
2015-09-30 15:47:58 Martin Packman bug added bug
2015-09-30 15:48:47 Martin Packman bug added subscriber Anastasia
2015-09-30 17:25:39 Martin Packman tags blocker ci test-failure windows blocker ci intermittent-failure test-failure windows
2015-09-30 18:14:37 Martin Packman summary stateSuite setup fails on windows with WSARecv timeout Test suite failures on windows with WSARecv timeout
2015-09-30 18:14:37 Martin Packman description CI windows tests on master are failing with "WSARecv tcp [::1]:51033: i/o timeout" in stateSuite test setup. <http://reports.vapour.ws/releases/3122/job/run-unit-tests-win2012-amd64/attempt/1316> FAIL: state_test.go:23: stateSuite.SetUpTest ... [LOG] 0:07.593 INFO juju.mongo dialled mongo successfully on address "[::1]:50712" [LOG] 0:26.352 DEBUG juju.apiserver -> [18] machine-0 21.0019446s {"RequestId":1,"Error":"WSARecv tcp [::1]:51033: i/o timeout","Response":"'body redacted'"} Admin[""].Login state_test.go:24: s.firewallerSuite.SetUpTest(c) c:/users/admini~1/appdata/local/temp/tmp6pllox/gogo/src/github.com/juju/juju/juju/testing/conn.go:152: c.Assert(err, jc.ErrorIsNil) ... value *errors.Err = &errors.Err{message:"", cause:(*params.Error)(0xc08433bc20), previous:(*params.Error)(0xc08433bc20), file:"github.com/juju/juju/api/state.go", line:79} ("WSARecv tcp [::1]:51033: i/o timeout") ... error stack: WSARecv tcp [::1]:51033: i/o timeout github.com/juju/juju/api/state.go:79: The only change in this window is 0061b9839bb5e7f36d4d0b8855420c42cda953fa from pr #3398. CI windows tests on have failed at various points with "WSARecv tcp [::1]:51033: i/o timeout", in test setup or during runs. <http://reports.vapour.ws/releases/3122/job/run-unit-tests-win2012-amd64/attempt/1316> FAIL: state_test.go:23: stateSuite.SetUpTest ... [LOG] 0:07.593 INFO juju.mongo dialled mongo successfully on address "[::1]:50712" [LOG] 0:26.352 DEBUG juju.apiserver -> [18] machine-0 21.0019446s {"RequestId":1,"Error":"WSARecv tcp [::1]:51033: i/o timeout","Response":"'body redacted'"} Admin[""].Login state_test.go:24: s.firewallerSuite.SetUpTest(c) c:/users/admini~1/appdata/local/temp/tmp6pllox/gogo/src/github.com/juju/juju/juju/testing/conn.go:152: c.Assert(err, jc.ErrorIsNil) ... value *errors.Err = &errors.Err{message:"", cause:(*params.Error)(0xc08433bc20), previous:(*params.Error)(0xc08433bc20), file:"github.com/juju/juju/api/state.go", line:79} ("WSARecv tcp [::1]:51033: i/o timeout") ... error stack: WSARecv tcp [::1]:51033: i/o timeout github.com/juju/juju/api/state.go:79: Does not seem to be tied to a particular revision, but another general symptom of illness like connection shutdown panics.
2015-09-30 18:14:37 Martin Packman tags blocker ci intermittent-failure test-failure windows ci intermittent-failure test-failure windows
2015-09-30 18:14:47 Martin Packman juju-core: importance Critical High
2016-04-24 17:46:08 Curtis Hovey description CI windows tests on have failed at various points with "WSARecv tcp [::1]:51033: i/o timeout", in test setup or during runs. <http://reports.vapour.ws/releases/3122/job/run-unit-tests-win2012-amd64/attempt/1316> FAIL: state_test.go:23: stateSuite.SetUpTest ... [LOG] 0:07.593 INFO juju.mongo dialled mongo successfully on address "[::1]:50712" [LOG] 0:26.352 DEBUG juju.apiserver -> [18] machine-0 21.0019446s {"RequestId":1,"Error":"WSARecv tcp [::1]:51033: i/o timeout","Response":"'body redacted'"} Admin[""].Login state_test.go:24: s.firewallerSuite.SetUpTest(c) c:/users/admini~1/appdata/local/temp/tmp6pllox/gogo/src/github.com/juju/juju/juju/testing/conn.go:152: c.Assert(err, jc.ErrorIsNil) ... value *errors.Err = &errors.Err{message:"", cause:(*params.Error)(0xc08433bc20), previous:(*params.Error)(0xc08433bc20), file:"github.com/juju/juju/api/state.go", line:79} ("WSARecv tcp [::1]:51033: i/o timeout") ... error stack: WSARecv tcp [::1]:51033: i/o timeout github.com/juju/juju/api/state.go:79: Does not seem to be tied to a particular revision, but another general symptom of illness like connection shutdown panics. CI windows tests on have failed at various points with "WSARecv tcp [::1]:51033: i/o timeout", in test setup or during runs. <http://reports.vapour.ws/releases/issue/560bfec0749a562d81ebf836> FAIL: state_test.go:23: stateSuite.SetUpTest ... [LOG] 0:07.593 INFO juju.mongo dialled mongo successfully on address "[::1]:50712" [LOG] 0:26.352 DEBUG juju.apiserver -> [18] machine-0 21.0019446s {"RequestId":1,"Error":"WSARecv tcp [::1]:51033: i/o timeout","Response":"'body redacted'"} Admin[""].Login state_test.go:24:     s.firewallerSuite.SetUpTest(c) c:/users/admini~1/appdata/local/temp/tmp6pllox/gogo/src/github.com/juju/juju/juju/testing/conn.go:152:     c.Assert(err, jc.ErrorIsNil) ... value *errors.Err = &errors.Err{message:"", cause:(*params.Error)(0xc08433bc20), previous:(*params.Error)(0xc08433bc20), file:"github.com/juju/juju/api/state.go", line:79} ("WSARecv tcp [::1]:51033: i/o timeout") ... error stack:  WSARecv tcp [::1]:51033: i/o timeout  github.com/juju/juju/api/state.go:79: Does not seem to be tied to a particular revision, but another general symptom of illness like connection shutdown panics.
2016-04-24 17:46:31 Curtis Hovey tags ci intermittent-failure test-failure windows centos ci go1.6 intermittent-failure test-failure windows
2016-04-29 20:23:33 Curtis Hovey tags centos ci go1.6 intermittent-failure test-failure windows blocker centos ci go1.6 intermittent-failure test-failure windows
2016-05-02 16:09:15 Katherine Cox-Buday summary Test suite failures on windows with WSARecv timeout Test suite failures with WSARecv timeout
2016-05-02 16:09:15 Alexis Bruemmer juju-core: milestone 2.0-beta7
2016-05-02 16:09:16 Curtis Hovey tags blocker centos ci go1.6 intermittent-failure test-failure windows blocker centos ci go1.6 test-failure
2016-05-02 16:09:22 Curtis Hovey tags blocker centos ci go1.6 test-failure blocker centos ci go1.6 ppc64el test-failure
2016-05-02 16:26:09 Curtis Hovey juju-core: importance High Critical
2016-05-04 06:03:36 Andrew Wilkins juju-core: status Triaged In Progress
2016-05-04 06:03:39 Andrew Wilkins juju-core: assignee Andrew Wilkins (axwalk)
2016-05-05 01:58:25 Andrew Wilkins juju-core: status In Progress Fix Committed
2016-05-05 18:27:27 Curtis Hovey juju-core: status Fix Committed Fix Released
2016-08-23 01:02:05 Canonical Juju QA Bot affects juju-core juju
2016-08-23 01:02:05 Canonical Juju QA Bot juju: milestone 2.0-beta7
2016-08-23 01:02:07 Canonical Juju QA Bot juju: milestone 2.0-beta7