[Testbot] Plone 4.3 - Python 2.7 - Build # 2085 - Regression! - 1 failure(s)

jenkins at plone.org jenkins at plone.org
Mon Mar 24 04:06:27 UTC 2014


-------------------------------------------------------------------------------
Plone 4.3 - Python 2.7 - Build # 2085 - Failure!
-------------------------------------------------------------------------------

http://jenkins.plone.org/job/plone-4.3-python-2.7/2085/


-------------------------------------------------------------------------------
CHANGES
-------------------------------------------------------------------------------

Repository: plone.app.form
Branch: refs/heads/2.2.x
Date: 2014-03-23T20:16:01-07:00
Author: David Glick (davisagli) <david at glicksoftware.com>
Commit: https://github.com/plone/plone.app.form/commit/bf770555eee120b186219fa6cbd41006e7f87582

But the fourth one stayed up. And that's what you're going to get, Lad, the strongest castle in all of England.

Files changed:
M plone/app/form/widgets/datecomponents.txt

diff --git a/plone/app/form/widgets/datecomponents.txt b/plone/app/form/widgets/datecomponents.txt
index ba6c588..9041f91 100644
--- a/plone/app/form/widgets/datecomponents.txt
+++ b/plone/app/form/widgets/datecomponents.txt
@@ -14,10 +14,10 @@ if a date is created with a "-" instead of a "/". Dates
 that enter here with a "-" go to "GMT-0" by default whereas "/" goes to
 the server timezone (in my case this is "US/Pacific"). The bug:
 
-Note that this explanation won't work on certain timezones and
+Note that this test won't work on certain timezones and
 DateTime doesn't look at anything obvious to get the timezone
 info (like environment variables) so I'm going to patch the func
-that sets the timezone so that this explanation test doesn't
+that sets the timezone so that this test doesn't
 break on different timezones. If this test does break then, it
 means that the actual bug has been fixed. There maybe other signs
 such as pigs flying, locusts, etc...
@@ -29,7 +29,6 @@ such as pigs flying, locusts, etc...
   ...    return TEST_TIME_ZONE
   >>> DateTime.DateTime.localZone = fakeLocalZone
 
-
   >>> him = DateTime.DateTime("2011/01/13")
   >>> her = DateTime.DateTime("2011-01-13")
   >>> her == him
@@ -89,7 +88,7 @@ test case doesn't fail):
   (2011, '01', '12', '22', '30')
 
 And to be sure, we also can't break other tz representations. I won't test
-for time here because it will break half of every year do to daylight savings.
+for time here because it will break half of every year due to daylight savings.
 
   >>> date = "2011/01/13 01:30 US/Pacific"
   >>> parts = view.result(date=date)
@@ -146,12 +145,18 @@ Test date before 2499
   >>> parseDate(parts)
   (2499, '12', '30', '08', '00')
 
-Test date after 2500
+Test date after 2500. First we need to make sure that PLONE_CEILING
+is in our fake test timezone, so that it doesn't get converted
+to a time that will vary depending on the timezone in which the
+test is run.
+
+  >>> from plone.app.form.widgets import datecomponents
+  >>> datecomponents.PLONE_CEILING = DateTime.DateTime(2500, 0)
 
   >>> date = "2501-01-30 22:00 US/Pacific"
   >>> parts = view.result(date=date)
   >>> parseDate(parts)
-  (2499, '12', '30', '20', '00')
+  (2499, '12', '31', '00', '00')
 
 un-monkey patch
   >>> DateTime.DateTime.localZone = realLocalZone




-------------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CHANGES.log
Type: application/octet-stream
Size: 2744 bytes
Desc: not available
URL: <http://lists.plone.org/pipermail/plone-testbot/attachments/20140324/2d929ef0/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build.log
Type: application/octet-stream
Size: 81662 bytes
Desc: not available
URL: <http://lists.plone.org/pipermail/plone-testbot/attachments/20140324/2d929ef0/attachment-0003.obj>


More information about the Testbot mailing list