Use separate time values for 32 and 64 bit systems in feature tests

Use separate time values for 32 and 64 bit systems in feature tests

Some test cases fail due to updates to the time conversion
functions - https://codereview.chromium.org/1988663002/

The problem is that linux_chromium_dbg_32 starts to fail,
when the above mentioned CL is applied, because the date
after 2038 cannot be properly converted on 32-bit systems
due to 2^32 value limitation.

Committed: https://crrev.com/82bb85e827bc47c2918bd77fb8ec81bac68d4146
Cr-Commit-Position: refs/heads/master@{#399715}

[maksims (do not use this acc), 2016-06-13 09:43:29]

Description was changed from

==========
32bit

BUG=
==========

to

==========
Use separate time values for 32 and 64 bit systems.

Some test cases fail due to updates to the time conversion 
functions - https://codereview.chromium.org/1988663002/ 

The problem is that linux_chromium_dbg_32 starts to fail,
when the above mentioned CL is applied, because the date 
after 2038 cannot be properly converted on 32-bit systems
due to 2^32 value limitation.
==========

[maksims (do not use this acc), 2016-06-13 09:43:29]

maksim.sisov@intel.com changed reviewers:
+ cpu@chromium.org, finnur@chromium.org

[maksims (do not use this acc), 2016-06-13 09:50:17]

Description was changed from

==========
Use separate time values for 32 and 64 bit systems.

Some test cases fail due to updates to the time conversion 
functions - https://codereview.chromium.org/1988663002/ 

The problem is that linux_chromium_dbg_32 starts to fail,
when the above mentioned CL is applied, because the date 
after 2038 cannot be properly converted on 32-bit systems
due to 2^32 value limitation.
==========

to

==========
Use separate time values for 32 and 64 bit systems in feature tests

Some test cases fail due to updates to the time conversion 
functions - https://codereview.chromium.org/1988663002/ 

The problem is that linux_chromium_dbg_32 starts to fail,
when the above mentioned CL is applied, because the date 
after 2038 cannot be properly converted on 32-bit systems
due to 2^32 value limitation.
==========

[maksims (do not use this acc), 2016-06-13 10:03:58]

please review

[maksims (do not use this acc), 2016-06-14 05:38:33]

ping

[Finnur, 2016-06-14 13:14:58]

Sorry, an on offsite so slow to respond. 

LGTM

[Finnur, 2016-06-14 13:15:20]

> Sorry, an on offsite so slow to respond. 

Am* on

[maksims (do not use this acc), 2016-06-14 15:02:53]

The CQ bit was checked by maksim.sisov@intel.com

[commit-bot: I haz the power, 2016-06-14 15:03:24]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2060803002/20001

[commit-bot: I haz the power, 2016-06-14 15:41:23]

Description was changed from

==========
Use separate time values for 32 and 64 bit systems in feature tests

Some test cases fail due to updates to the time conversion 
functions - https://codereview.chromium.org/1988663002/ 

The problem is that linux_chromium_dbg_32 starts to fail,
when the above mentioned CL is applied, because the date 
after 2038 cannot be properly converted on 32-bit systems
due to 2^32 value limitation.
==========

to

==========
Use separate time values for 32 and 64 bit systems in feature tests

Some test cases fail due to updates to the time conversion 
functions - https://codereview.chromium.org/1988663002/ 

The problem is that linux_chromium_dbg_32 starts to fail,
when the above mentioned CL is applied, because the date 
after 2038 cannot be properly converted on 32-bit systems
due to 2^32 value limitation.
==========

[commit-bot: I haz the power, 2016-06-14 15:41:24]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-06-14 15:52:19]

Description was changed from

==========
Use separate time values for 32 and 64 bit systems in feature tests

Some test cases fail due to updates to the time conversion 
functions - https://codereview.chromium.org/1988663002/ 

The problem is that linux_chromium_dbg_32 starts to fail,
when the above mentioned CL is applied, because the date 
after 2038 cannot be properly converted on 32-bit systems
due to 2^32 value limitation.
==========

to

==========
Use separate time values for 32 and 64 bit systems in feature tests

Some test cases fail due to updates to the time conversion
functions - https://codereview.chromium.org/1988663002/

The problem is that linux_chromium_dbg_32 starts to fail,
when the above mentioned CL is applied, because the date
after 2038 cannot be properly converted on 32-bit systems
due to 2^32 value limitation.

Committed: https://crrev.com/82bb85e827bc47c2918bd77fb8ec81bac68d4146
Cr-Commit-Position: refs/heads/master@{#399715}
==========

[commit-bot: I haz the power, 2016-06-14 15:52:20]

Patchset 2 (id:??) landed as
https://crrev.com/82bb85e827bc47c2918bd77fb8ec81bac68d4146
Cr-Commit-Position: refs/heads/master@{#399715}