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

test failure: test_dt_two_tz #382

Closed
lfam opened this issue Mar 21, 2016 · 7 comments
Closed

test failure: test_dt_two_tz #382

lfam opened this issue Mar 21, 2016 · 7 comments

Comments

@lfam
Copy link
Contributor

lfam commented Mar 21, 2016

While building khal 0.7.0 in GNU Guix, the build process fails during the test suite due to the failure of test_dt_two_tz.

Specifically, this assertion fails:
assert ('VCALENDAR',...set([]))]))])) == ('VCALENDAR', ...set([]))]))]))

I've attached the verbose output of that test, and the dependency graph that is used to build khal, excluding implicit inputs such as tar, GCC, etc.

Please let me know if I can provide more information, run other tests, or anything like that.

khal-verbose-failure-output.txt
graph.txt

@geier
Copy link
Member

geier commented Mar 21, 2016

Thanks, we need to wrap that test with freeze_time.

@lfam
Copy link
Contributor Author

lfam commented Mar 21, 2016

Okay.

Do you think it's safe to disable the test in our packaging? Is it a race / TOCTTOU bug in the tests?

@geier
Copy link
Member

geier commented Mar 29, 2016

Yeas, this is save to disable. Until recently, after every Standard/Daylight-Saving-Time transition either in America/New_York or Europe/Berlin the tests had to be adapted. This is fixed in head.

I know I promised a new release some time ago, but there are still some bugs I want to squash before making a new release.

@lfam
Copy link
Contributor Author

lfam commented Mar 29, 2016

Okay, thanks for letting me know.

It's no problem for me to disable this test in our package until a new version of Khal is released.

@geier
Copy link
Member

geier commented Apr 25, 2016

@lfam are those gone for you?

@lfam
Copy link
Contributor Author

lfam commented Apr 26, 2016

Yes, they are gone in 0.8.1. Thanks!

@geier
Copy link
Member

geier commented Apr 26, 2016

Thanks for reporting and confirming.

@geier geier closed this as completed Apr 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants