Bug#934843: parsedatetime: FTBFS in stretch
Hi, On 1/30/21 12:54 AM, Santiago Vila wrote: > > I have not tested myself, but if this were my package I would try to > built it in 2019-08 (using "libfaketime" or something similar), as the > failure in the test suite seems to depend on the date on which it's > built. just done that with several of the timestamps that were marked as failed in your list - was not able reproduce that issue. I also remember that I gave it a try shortly after you've opened that bug, and it just built fine. So if you have any more clues on how to reproduce that issue, I'd be all happy to try it. Bernd -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bug#934843: parsedatetime: FTBFS in stretch
On Thu, 14 Nov 2019, Harlan Lieberman-Berg wrote: > tag 934843 +unreproducible > thanks > > On Thu, 15 Aug 2019 19:12:49 + Santiago Vila wrote: > > I tried to build this package in stretch but it failed: > > Hello! > > This is quite strange. I've tried rebuilding it several times in my > stretch sbuild, and it worked every time without error. I also > re-triggered the build on reproducible-builds, and it's now clean > there as well. > > One possibility that comes to mind is locales -- what locales are you > compiling under? It's possible there's a bug in one of the > locale-specific parsers that's not getting exercised on my sbuild, > through, I admit to not being sure how reproducible-builds could have > been affected by the same thing. Otherwise, maybe a difference in one > of the deps that was fixed in the last... day? Sprry for the late reply. I reported this in 2019-08 and the first reply came in 2019-11. By that time, the package built ok again in my autobuilders according to my build history: Status: successful parsedatetime_2.1-3+deb9u1_amd64-20190216T184806.957Z Status: successful parsedatetime_2.1-3+deb9u1_amd64-20190319T030404.993Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T104812.785Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115932.874Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115928.188Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115932.124Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115937.789Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115954.716Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T120006.211Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115946.514Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T120019.561Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T115949.086Z Status: failed parsedatetime_2.1-3+deb9u1_amd64-20190812T120022.496Z Status: successful parsedatetime_2.1-3+deb9u1_amd64-20191018T145214.267Z Status: successful parsedatetime_2.1-3+deb9u1_amd64-20191018T172715.052Z Status: successful parsedatetime_2.1-3+deb9u1_amd64-20200210T050524.951Z Status: successful parsedatetime_2.1-3+deb9u1_amd64-20200305T171505.547Z Status: successful parsedatetime_2.1-3+deb9u1_amd64-20200720T162707.522Z However, by looking at the build log and the kind of error, I believe it's the kind of date-related bug in the test suite which only happens in certain times of the year. Does this make sense? Why would this happen if not? Result: (time.struct_time(tm_year=2019, tm_mon=8, tm_mday=22, tm_hour=3, tm_min=26, tm_sec=0, +tm_wday=0, tm_yday=224, tm_isdst=-1), 3) Expected: (time.struct_time(tm_year=2020, tm_mon=8, tm_mday=22, tm_hour=3, tm_min=26, tm_sec=0, +tm_wday=5, tm_yday=235, tm_isdst=-1), 3) I have not tested myself, but if this were my package I would try to built it in 2019-08 (using "libfaketime" or something similar), as the failure in the test suite seems to depend on the date on which it's built. (I'm not reopening the bug, but I believe this little extra information belongs to the bug report). Thanks.
Bug#934843: parsedatetime: FTBFS in stretch
tag 934843 +unreproducible thanks On Thu, 15 Aug 2019 19:12:49 + Santiago Vila wrote: > I tried to build this package in stretch but it failed: Hello! This is quite strange. I've tried rebuilding it several times in my stretch sbuild, and it worked every time without error. I also re-triggered the build on reproducible-builds, and it's now clean there as well. One possibility that comes to mind is locales -- what locales are you compiling under? It's possible there's a bug in one of the locale-specific parsers that's not getting exercised on my sbuild, through, I admit to not being sure how reproducible-builds could have been affected by the same thing. Otherwise, maybe a difference in one of the deps that was fixed in the last... day? Sincerely, -- Harlan Lieberman-Berg ~hlieberman
Bug#934843: parsedatetime: FTBFS in stretch
Package: src:parsedatetime Version: 2.1-3+deb9u1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in stretch but it failed: [...] debian/rules build-indep dh build-indep --with python2,python3 --buildsystem pybuild dh_testdir -i -O--buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:184: python2.7 setup.py config running config I: pybuild base:184: python3.5 setup.py config running config dh_auto_build -i -O--buildsystem=pybuild I: pybuild base:184: /usr/bin/python setup.py build running build running build_py creating /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime copying parsedatetime/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime copying parsedatetime/parsedatetime.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime copying parsedatetime/context.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime copying parsedatetime/warns.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime creating /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/nl_NL.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/base.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/icu.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/ru_RU.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/de_DE.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/en_AU.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/__init__.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/es.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/en_US.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/pt_BR.py -> /<>/.pybuild/pythonX.Y_2.7/build/parsedatetime/pdt_locales I: pybuild base:184: /usr/bin/python3 setup.py build running build running build_py creating /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime copying parsedatetime/__init__.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime copying parsedatetime/parsedatetime.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime copying parsedatetime/context.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime copying parsedatetime/warns.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime creating /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/nl_NL.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/base.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/icu.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/ru_RU.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/de_DE.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/en_AU.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/__init__.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/es.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/en_US.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales copying parsedatetime/pdt_locales/pt_BR.py -> /<>/.pybuild/pythonX.Y_3.5/build/parsedatetime/pdt_locales dh_auto_test -i -O--buildsystem=pybuild I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m nose tests .F...SSSSSS == FAIL: testDates (tests.TestComplexDateTimes.test) -- Traceback (most recent call last): File "/<>/.pybuild/pythonX.Y_2.7/build/tests/TestComplexDateTimes.py", line 145, in testDates self.cal.parse('August 22nd 3:26', start), (target, 3)) File "/<>/.pybuild/pythonX.Y_2.7/build/tests/utils.py", line 22, in decoratedComparator self.fail(failureMessage % (errMsg, result, check)) AssertionError: Result does not match target value Result: (time.struct_time(tm_year=2019, tm_mon=8, tm_mday=22, tm_hour=3, tm_min=26, tm_sec=0, tm_wday=0, tm_yday=224, tm_isdst=-1), 3) Expected: (time.struct_time(tm_year=2020, tm_mon=8, tm_mday=22, tm_hour=3, tm_min=26, tm_sec=0, tm_wday=5, tm_yday=235, tm_isdst=-1), 3)