NotImplementedError: DatetimeProperty sheriff_action_time can only support UTC. Please derive a new Property to support alternative timezones. |
||||
Issue descriptionThe cron job for "/waterfall/check-reverted-cls" failed to the this error. You could manually trigger a run by visiting the url directly.
,
Mar 21 2017
,
Mar 21 2017
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/c343591bfae64af558178eaffdb64a8a79022f00 commit c343591bfae64af558178eaffdb64a8a79022f00 Author: Jeffrey Li <lijeffrey@chromium.org> Date: Tue Mar 21 20:10:59 2017 [Findit] Fixing Revert.timestamp not to use timezone BUG= 703502 It seems the timestamp returned from time_util.UTCDatetimeFromNaiveString is in the format datetime.datetime(2017, 3, 19, 1, 28, 20, 351410, tzinfo=<UTC>), with "tzinfo=<UTC>" throwing the exception when calling .put(). It appears the timestamps in Rietveld are already in UTC, making this unnecessary and just DatetimeFromString suffices and is in a format that can be written to the datastore. Change-Id: I8e7e797109bb709afd9d5325bdc2648cc2228470 Reviewed-on: https://chromium-review.googlesource.com/457294 Commit-Queue: Jeffrey Li <lijeffrey@chromium.org> Reviewed-by: Roberto Carrillo <robertocn@chromium.org> [modify] https://crrev.com/c343591bfae64af558178eaffdb64a8a79022f00/appengine/findit/infra_api_clients/codereview/rietveld.py [modify] https://crrev.com/c343591bfae64af558178eaffdb64a8a79022f00/appengine/findit/infra_api_clients/codereview/test/rietveld_test.py
,
Mar 21 2017
,
Apr 12 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by st...@chromium.org
, Mar 21 2017