[prop250] Fix a time parsing error on platforms with 32 bit time_t

On platforms with 32 bit time_t, tor can't parse some dates in 2038, and all dates after 2038. So using 2666 in test data doesn't work.

My branch sr-32bit on https://github.com/teor2345/tor.git fixes this issue, which is T9 from #16943 (moved).

changed milestone to %Tor: 0.2.9.x-final

added TorCoreTeam201605 actualpoints::0.1 component::core tor/tor milestone::Tor: 0.2.9.x-final owner::teor parent::16943 points::0.1 priority::medium resolution::fixed severity::normal status::closed tor-hs type::defect labels

Trac:
Status: new to assigned
Owner: N/A to teor

Trac:
Status: assigned to needs_review

Create a review-group-2 from (most of the) tickets in 0.2.8 or 0.2.9 or 029-nickm-says-yes listed as needs_review,

Trac:
Keywords: N/A deleted, review-group-2 added

Trac:
Reviewer: N/A to nickm

wait, nm, this is on prop250.

Trac:
Reviewer: nickm to N/A
Summary: Fix a time parsing error on platforms with 32 bit time_t to [prop250] Fix a time parsing error on platforms with 32 bit time_t

FWIW, this is a patch on top of the prop250 branch.

I included this fix in my #16943 (moved) branch (see comment:72:ticket:16943). We can close this ticket once that gets merged.

For now I remove it from review-group-2, since it's part of the prop250 giant.

Trac:
Keywords: review-group-2 deleted, N/A added

I just cherry-picked asn's commit into the branch that I'll be submitting for review today. Putting this ticket as resolved since the review will now happen in the #16943 (moved) (or as asn puts it, the prop250 giant).

Trac:
Resolution: N/A to fixed
Status: needs_review to closed

closed

changed time estimate to 48m

added 48m of time spent

moved to tpo/core/tor#19125 (closed)