Mailing List Archive

This is the summary for test reports received on the
zope-tests list between 2016-04-01 00:00:00 UTC and 2016-04-02 00:00:00 UTC:

See the footnotes for test reports of unsuccessful builds.

An up-to date view of the builders is also available in our
buildbot documentation:
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds

Reports received
----------------

[1] winbot / ZODB_dev py_265_win32
[2] winbot / ZODB_dev py_265_win64
[3] winbot / ZODB_dev py_270_win32
[4] winbot / ZODB_dev py_270_win64
[5] winbot / ztk_10 py_254_win32
winbot / ztk_10 py_265_win32
winbot / ztk_10 py_265_win64
winbot / ztk_11 py_265_win32
winbot / ztk_11 py_265_win64
winbot / ztk_11 py_270_win32
winbot / ztk_11 py_270_win64

Non-OK results
--------------

[1] FAILED winbot / ZODB_dev py_265_win32
https://mail.zope.org/pipermail/zope-tests/2016-April/093154.html


[2] FAILED winbot / ZODB_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2016-April/093155.html


[3] FAILED winbot / ZODB_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2016-April/093152.html


[4] FAILED winbot / ZODB_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2016-April/093153.html


[5] FAILED winbot / ztk_10 py_254_win32
https://mail.zope.org/pipermail/zope-tests/2016-April/093156.html


_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/02/2016 07:00 PM, Zope tests summarizer wrote:
> [1] FAILED winbot / ZODB_dev py_265_win32
> https://mail.zope.org/pipermail/zope-tests/2016-April/093154.html
>
>
> [2] FAILED winbot / ZODB_dev py_265_win64
> https://mail.zope.org/pipermail/zope-tests/2016-April/093155.html
>
>
> [3] FAILED winbot / ZODB_dev py_270_win32
> https://mail.zope.org/pipermail/zope-tests/2016-April/093152.html
>
>
> [4] FAILED winbot / ZODB_dev py_270_win64
> https://mail.zope.org/pipermail/zope-tests/2016-April/093153.html

All four are the same failure:

- ------------------------------ %< ----------------------------------------
Failure in test
c:\buildslave\zodb_dev_py_265_win32\build\src\ZODB\historical_connections.t
xt

- ----------------------------------------------------------------------
File
"c:\buildslave\zodb_dev_py_265_win32\build\src\ZODB\historical_connections.
txt",
line 220, in historical_connections.txt
Failed example:
[c in conns1 for c in conns2]
Expected:
[False, False, True, True]
Got:
[False, False, False, True]

- ------------------------------ %< ----------------------------------------


> [5] FAILED winbot / ztk_10 py_254_win32
> https://mail.zope.org/pipermail/zope-tests/2016-April/093156.html

I wish I could work out how to get the 'pyh_254' tests turned off altogethe
r.


Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJXAFNgAAoJEPKpaDSJE9HY6QYP/3sCNrpSCVQUUtb7+ZdZLVEa
gOXIdE8G6pruersNfXlTLKpDujAwW6bvm79ZywZRMtTcO3/MWkiOrArDOObT1FMD
g9cLFi11JHwh1Tl922sTQc5CW3V3W+RtvUWDseE+nqG2/IqsUN+WRxzzZzpW/582
DY3kGgxbA5EZjkzf8yFtLE8ES9dsyObTg/Z6ARsEg5kvFbbuitMQspbp9uLWklLl
UG3Y2F0dczu6XPXAzNJOyDfOPXLc0ZOhacTw9YMks21C7OVuaS99agrDVJ8bd7O0
CGl5AkFt6SG1AANnoNTyH60j7Goaidd304x6XbF4vX60cL0TAUkA8s2L1uvXiitN
1Xdzv+R4HE42/X9dbYDOSebJwgy6CYdBEiGlAyZBwaWTNV37Y8rLRZRe34wR5jHF
m8FxI9Xioalj3flwtm0qBdkqgDzvwETDtH3yqQ/JMNNZMsycFtXUqnP8Dmu2wg9f
acChY5HPixpv7t1jFRWqJPeWUhrDShcRRl4+k3YJxPwuJ5FGY5T0E70zPUDF40U7
GQFN6+H2Fe9sH1ivzW/lI0ZF+lI+0/p5W1amDVkfFEBm5gk760IwLTF2v6HbYOKL
p4dD6NEx1J+eEjC6cgetLYc/RChLkVLwzGvBNfP2if059U8CBunvsPqV9Ev615dr
x03UEMxingAaEecjISze
=RM8u
-----END PGP SIGNATURE-----

_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )

> On Apr 2, 2016, at 18:19, Tres Seaver <tseaver@palladion.com> wrote:
>
> On 04/02/2016 07:00 PM, Zope tests summarizer wrote:
>> [1] FAILED winbot / ZODB_dev py_265_win32
>> https://mail.zope.org/pipermail/zope-tests/2016-April/093154.html
>>
>>
>> [2] FAILED winbot / ZODB_dev py_265_win64
>> https://mail.zope.org/pipermail/zope-tests/2016-April/093155.html
>>
>>
>> [3] FAILED winbot / ZODB_dev py_270_win32
>> https://mail.zope.org/pipermail/zope-tests/2016-April/093152.html
>>
>>
>> [4] FAILED winbot / ZODB_dev py_270_win64
>> https://mail.zope.org/pipermail/zope-tests/2016-April/093153.html
>
> All four are the same failure:
>
> - ------------------------------ %< ----------------------------------------
> Failure in test
> c:\buildslave\zodb_dev_py_265_win32\build\src\ZODB\historical_connections.t
> xt
>
> - ----------------------------------------------------------------------
> File
> "c:\buildslave\zodb_dev_py_265_win32\build\src\ZODB\historical_connections.
> txt",
> line 220, in historical_connections.txt
> Failed example:
> [c in conns1 for c in conns2]
> Expected:
> [False, False, True, True]
> Got:
> [False, False, False, True]
>
> - ------------------------------ %< ----------------------------------------

I've seen this locally, occasionally, and it's failed like this on the buildbot before too.

This test is relying on time.time() and time.sleep() to do its thing:

>>> db2.setHistoricalTimeout(.01)
>>> time.sleep(.1)
>>> conns2[2].close(); conns2[3].close()
....
>>> conns1 = [db2.open(before=serial) for i in range(4)]

As far as I can see (but I'm not a doctest expert), these functions aren't monkey-patched in this test the way that time.time, at least, is patched in, say, src/ZODB/DemoStorage.test (below). Perhaps they should be? I can open a copy-and-paste PR to do so.

.. We need to mess with time to prevent spurious test failures on windows

>>> now = 1231019584.0
>>> def faux_time_time():
... global now
... now += .1
... return now
>>> import time
>>> real_time_time = time.time
>>> if isinstance(time,type):
... time.time = staticmethod(faux_time_time) # Jython
... else:
... time.time = faux_time_time

>
>> [5] FAILED winbot / ztk_10 py_254_win32
>> https://mail.zope.org/pipermail/zope-tests/2016-April/093156.html
>
> I wish I could work out how to get the 'pyh_254' tests turned off altogethe
> r.

+1. And also for the ZODB_dev py_265 tests too, because ZODB no longer supports 2.6 (https://github.com/zopefoundation/ZODB/pull/48).

Jason
_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/03/2016 08:07 AM, Jason Madden wrote:
> As far as I can see (but I'm not a doctest expert), these functions
> aren't monkey-patched in this test the way that time.time, at least,
> is patched in, say, src/ZODB/DemoStorage.test (below). Perhaps they
> should be? I can open a copy-and-paste PR to do so.
>
> .. We need to mess with time to prevent spurious test failures on
> windows
>
>>>> now = 1231019584.0 def faux_time_time():
> ... global now ... now += .1 ... return now
>>>> import time real_time_time = time.time if
>>>> isinstance(time,type):
> ... time.time = staticmethod(faux_time_time) # Jython ... else: ...
> time.time = faux_time_time


Hmm, that looks like it could work -- when I looked at the test
yesterday, I wondered if there were a race condition going on due to load
on the machine.


Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJXAQutAAoJEPKpaDSJE9HYmp4P/0oEzS5m7rfvZ3aAXTgEz2hM
Dc0N6s0xLO8xmKohgxKQssb71kj0wjfCuOwgjGCTAOcwc/4aaIymv1PcSPoywZSE
FJyFs6tWxkn7hsbuZqKoPD4AoUGHhO/lgPkbXGnK2vs+3mRDv4on8pi1/Aghm2Xw
HkDnMEK8dlvsoWbtEp9jvj/1hnD5ArR44aMy0KT9dYtfnZ2TmoFQJ/L7glCVuRzu
Llb4nSrctabapqf4g+oDHC1zAuGeaBW/Zlwd5qV14Bt7FbMsJ5rOCgj9tmFNsSMt
s9FAtc34V0BRq8SUXixoWXFH7umO73KwPtb3wnlKze/ioN/JEin84DIpcnPUFO/A
teC47MGePPkh4BiaSpxqzq5I9PUH7XyUVibyO3A3RykJlO4jBErym9goYfy/iuZa
RhF7OWY4ZdMr0x9YiGpttCU0HUR6xifZYrvDA0uuGE216urG19cFYdzJRwfj3Ttp
bu+PZBk+AFMQPRQp4rnRnMkLWZd2iOT52NOBDJ79q6ov8GJer2VXG8aHvAVffaXq
ZH0MvCAZV+2C58hWgiWMDysg5GhOpADCscMIsI8yhv3fUEa2bGucfor2yZpj/tJk
rhTeRXQ0mkepivkFnKHDv7KpDdxGBrwUcpFyFAVTZjUhnEL1uZn8jCHsnuoJpRsh
lh7wUYIxVFdqenLQ2wxi
=4Ng0
-----END PGP SIGNATURE-----

_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )

> On Apr 3, 2016, at 07:25, Tres Seaver <tseaver@palladion.com> wrote:
>
> Hmm, that looks like it could work -- when I looked at the test
> yesterday, I wondered if there were a race condition going on due to load
> on the machine.

https://github.com/zopefoundation/ZODB/pull/51

Now all the builds *consistently* fail with the original error ([False,False,False,True]). That's progress, I guess? More comments on the PR.

Jason
_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )