groovy
  1. groovy
  2. GROOVY-3325

DurationTest fails for several time zones

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.6-rc-2
    • Fix Version/s: 1.6.5
    • Component/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      groovy.time.DurationTest fails in the following time zones:

      America/Adak
      America/Atka
      US/Aleutian
      AST
      America/Anchorage
      America/Juneau
      America/Nome
      America/Yakutat
      US/Alaska
      America/Dawson
      America/Los_Angeles
      America/Vancouver
      America/Whitehorse
      Canada/Pacific
      Canada/Yukon
      PST
      PST8PDT
      US/Pacific
      US/Pacific-New
      America/Boise
      America/Cambridge_Bay
      America/Denver
      America/Edmonton
      America/Inuvik
      America/Shiprock
      America/Yellowknife
      Canada/Mountain
      MST7MDT
      Navajo
      US/Mountain
      America/Chicago
      America/Indiana/Knox
      America/Indiana/Tell_City
      America/Knox_IN
      America/Menominee
      America/North_Dakota/Center
      America/North_Dakota/New_Salem
      America/Rainy_River
      America/Rankin_Inlet
      America/Winnipeg
      CST
      CST6CDT
      Canada/Central
      US/Central
      US/Indiana-Starke
      America/Detroit
      America/Fort_Wayne
      America/Grand_Turk
      America/Indiana/Indianapolis
      America/Indiana/Marengo
      America/Indiana/Petersburg
      America/Indiana/Vevay
      America/Indiana/Vincennes
      America/Indiana/Winamac
      America/Indianapolis
      America/Iqaluit
      America/Kentucky/Louisville
      America/Kentucky/Monticello
      America/Louisville
      America/Montreal
      America/Nassau
      America/New_York
      America/Nipigon
      America/Pangnirtung
      America/Thunder_Bay
      America/Toronto
      Canada/Eastern
      EST5EDT
      IET
      US/East-Indiana
      US/Eastern
      US/Michigan
      America/Glace_Bay
      America/Goose_Bay
      America/Halifax
      America/Moncton
      America/Thule
      Antarctica/Palmer
      Atlantic/Bermuda
      Atlantic/Stanley
      Canada/Atlantic
      America/St_Johns
      CNT
      Canada/Newfoundland
      AGT
      America/Argentina/Buenos_Aires
      America/Argentina/Cordoba
      America/Argentina/Tucuman
      America/Buenos_Aires
      America/Cordoba
      America/Miquelon
      America/Rosario
      Africa/Windhoek
      Indian/Mauritius
      Australia/Adelaide
      Australia/Broken_Hill
      Australia/South
      Australia/Yancowinna
      AET
      Australia/ACT
      Australia/Canberra
      Australia/Currie
      Australia/Melbourne
      Australia/NSW
      Australia/Sydney
      Australia/Victoria
      Australia/LHI
      Australia/Lord_Howe
      Antarctica/McMurdo
      Antarctica/South_Pole
      NST
      NZ
      Pacific/Auckland
      NZ-CHAT
      Pacific/Chatham

        Activity

        Hide
        blackdrag blackdrag added a comment -

        I am setting the fix version to 1.6.1, because it is not a critical thing to fix for 1.6.0

        Show
        blackdrag blackdrag added a comment - I am setting the fix version to 1.6.1, because it is not a critical thing to fix for 1.6.0
        Hide
        blackdrag blackdrag added a comment -

        Have you any idea why the tests fail in these time zones?

        Show
        blackdrag blackdrag added a comment - Have you any idea why the tests fail in these time zones?
        Hide
        Alexander Veit added a comment -

        The fix version was set by accident. Sorry for that.

        The code that fails is a real brain twister. As far as an inferior earthling like me can understand, the poodle's quintessence is the comparison of two unrelated daylight savings offsets, one back in the seventies, and one in the new millenium. But don't take that for granted

        Show
        Alexander Veit added a comment - The fix version was set by accident. Sorry for that. The code that fails is a real brain twister. As far as an inferior earthling like me can understand, the poodle's quintessence is the comparison of two unrelated daylight savings offsets, one back in the seventies, and one in the new millenium. But don't take that for granted
        Hide
        Paul King added a comment -

        Currently the test is commented out on all branches. We need to re-enable them once fixed.

        Show
        Paul King added a comment - Currently the test is commented out on all branches. We need to re-enable them once fixed.
        Hide
        John Wagenleitner added a comment -

        Looks like the offending asserts were changed in commit d5d3914ca6 and those changes later reworked in commit 79fc734f89, should this issue be resolved/closed?

        Show
        John Wagenleitner added a comment - Looks like the offending asserts were changed in commit d5d3914ca6 and those changes later reworked in commit 79fc734f89 , should this issue be resolved/closed?
        Hide
        Paul King added a comment -

        Looks ok to me too but I tend to not use non-standard time zones much.

        Show
        Paul King added a comment - Looks ok to me too but I tend to not use non-standard time zones much.
        Hide
        Paul King added a comment -

        Assuming this was fixed in earlier commits as per recent comments. If the error still occurs, please reopen or raise another issue.

        Show
        Paul King added a comment - Assuming this was fixed in earlier commits as per recent comments. If the error still occurs, please reopen or raise another issue.

          People

          • Assignee:
            Paul King
            Reporter:
            Alexander Veit
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: