Buggy localtime() on Windows and 32-bit platforms
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
New
|
Undecided
|
Unassigned | ||
Breezy |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
[flext@web99 tb]$ python2.7 ../BZRR/
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "/home/
return the_callable(*args, **kwargs)
File "/home/
ret = run(*run_argv)
File "/home/
return self.run(
File "/home/
return self._operation
File "/home/
self.cleanups, self.func, *args, **kwargs)
File "/home/
result = func(*args, **kwargs)
File "/home/
result = func(*args, **kwargs)
File "/home/
Logger(b, rqst).show(lf)
File "/home/
self.
File "/home/
lf.
File "/home/
lines.
File "/home/
self.
File "/home/
_format_date(t, offset, timezone, date_fmt, show_offset)
File "/home/
tt = time.localtime(t)
ValueError: timestamp out of range for platform time_t
bzr 2.8.0dev1 on python 2.7.12 (Linux-
redhat-
arguments: ['../BZRR/
plugins: bash_completion
grep[
news_
encoding: 'utf-8', fsenc: 'UTF-8', lang: 'fr_FR.UTF-8'
Related branches
- bzr-core: Pending requested
-
Diff: 79 lines (+34/-5)3 files modifiedbzrlib/osutils.py (+19/-5)
bzrlib/tests/test_osutils.py (+12/-0)
doc/en/release-notes/bzr-2.8.txt (+3/-0)
Can you provide some more context on what is actually going wrong here? How can we reproduce this bug?