Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests fail in 2038 #8556

Closed
2 tasks done
bmwiedemann opened this issue Jan 3, 2023 · 2 comments
Closed
2 tasks done

tests fail in 2038 #8556

bmwiedemann opened this issue Jan 3, 2023 · 2 comments
Labels
wontfix Nobody will work on this.

Comments

@bmwiedemann
Copy link

Describe the issue

While working on reproducible builds for openSUSE, I found that
our weblate package failed to build in 2038, because a test failed:

ERROR: test_upstream_changes_rename (weblate.vcs.tests.test_vcs.VCSHgTest)
weblate.vcs.base.RepositoryException: hg: parse error: date exceeds 32 bits: 2180462939

Background:
As part of my work on reproducible builds for openSUSE, I check that software still gives identical build results in the future.
The usual offset is +16 years, because that is how long I expect some software will be used in some places.
This showed up failing tests in our package build.
See https://reproducible-builds.org/ for why this matters.

I already tried

  • I've read and searched the documentation.
  • I've searched for similar issues in this repository.

Steps to reproduce the behavior

  1. on Debian or openSUSE do
  2. osc co openSUSE:Factory/weblate && cd $_
  3. osc build --vm-type=kvm --noservice --clean --build-opt=--vm-custom-opt="-rtc base=2038-09-04T00:00:00" standard

Expected behavior

tests should keep passing in future

Screenshots

No response

Exception traceback

ERROR: test_upstream_changes_rename (weblate.vcs.tests.test_vcs.VCSHgTest)
weblate.vcs.base.RepositoryException: hg: parse error: date exceeds 32 bits: 2180462939

How do you run Weblate?

Other

Weblate versions

No response

Weblate deploy checks

No response

Additional context

No response

@nijel nijel added the wontfix Nobody will work on this. label Jan 4, 2023
@nijel
Copy link
Member

nijel commented Jan 4, 2023

@nijel nijel closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2023
@bmwiedemann
Copy link
Author

Thanks for the pointer. I filed https://bz.mercurial-scm.org/show_bug.cgi?id=6778

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix Nobody will work on this.
Projects
None yet
Development

No branches or pull requests

2 participants