Use the same date value in tests
Reported by
maksim.s...@intel.com,
Jun 14 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 Steps to reproduce the problem: After the following cl has landed - https://codereview.chromium.org/1988663002/ , some tests started to fail on linux dbg 32-bit bot: PolicyTest.PRE_DefaultCookiesSetting FeatureSwitchEnabledTest.TrueFieldTrialValue FeatureSwitchEnabledTest.FalseFieldTrialDogfoodValue FeatureSwitchEnabledTest.FalseFieldTrialValue FeatureSwitchEnabledTest.TrueFieldTrialDogfoodValue The workaround for the tests is to check if a system is 32 or 64 bit and use different year values for each of that. What is the expected behavior? Remove this check in the future. What went wrong? It is not possible to represent year 2039 and onwards in msecs on 32-bit system due to 2^32 restriction. Did this work before? N/A Chrome version: Channel: n/a OS Version: Flash Version:
,
Jul 13 2016
,
Jul 14 2016
Solved: https://codereview.chromium.org/2061633002/ https://codereview.chromium.org/2060803002 Sorry, forgotten to add the bug number there
,
Dec 16 2016
|
|||
►
Sign in to add a comment |
|||
Comment 1 by brajkumar@chromium.org
, Jun 15 2016