-
-
Notifications
You must be signed in to change notification settings - Fork 170
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
[BUG] problem with timezone tests on NetBSD #731
Comments
Thanks for reporting this. It seems we have an assumption that works on Debian:
I guess, this just needs a different function to compare datetime for equality. That would fix the tests. One could also add another operating system in the CI if that is wished for. I do not know how otherwise we will be able to prevent this in the future. |
I don't feel comfortable tackling this, since I don't know the code at all. I tried playing around with Python and got this far:
Is that what the test code is currently doing? These objects look quite different to me :-) The path to the zone file is the same on NetBSD:
|
I think, for now, I would assume that icalendar does work under that OS. However, the tests do not run because the timezones have a different module as origin. (1) I think that there should be some way to track this down. (2) But we can also make tests more generic. I like option 2. E.g. this line can be changed: assert exdate[i].dts[0].dt == in_timezone(exception_date, 'Europe/Vienna') to assert_datetime_is_in_timezone(exdate[i].dts[0].dt, exception_date, 'Europe/Vienna') and that makes sure that the datetime is equal and the timezone has the string 'Europe/Vienna' in it. I think, that is enough testing... identity of the timezones is not required but only an assumption here. We want the timezone object to be any 'Europe/Vienna' timezone and not necessarily be a ZoneInfo object. What are your thoughts on this? If you need any help to get this done, I am here. Your contribution is much appreciated! |
Could help with collective#731
Describe the bug
When running the self tests for 6.0.1 on NetBSD 10.99.12/amd64, there are about 20 self test failures due to timezone issues.
To Reproduce
One example of the detailed output of a test:
Expected behavior
No errors.
Environment
icalendar
version: 6.0.1Additional context
n/a
The text was updated successfully, but these errors were encountered: