-
Notifications
You must be signed in to change notification settings - Fork 37
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
Raise test coverage to 100% #92
Comments
I tried to come up with a test for... Lines 41 to 47 in d29d976
I even wrote a helper to iterate over date/time ranges, but I found no value which fails for the try block and succeeds for the except block. The change was introduced in be35566 @Beercow @petri Maybe you know or remember why this try/except statement was introduced in the first place? |
I don't remember. But I bet this is related: https://stackoverflow.com/questions/10849717/what-is-the-significance-of-january-1-1601 |
It has to do with an error where microseconds are too large
http://statgen.us/files/software/seqpower/usr/local/lib/anaconda2/pkgs/pillow-3.1.1-py27_0/lib/python2.7/site-packages/PIL/OleFileIO.py
Thank you in advance,
Brian Maloney, GCIH, GCFE, GCFA
… On Nov 28, 2020, at 12:42 PM, Jürgen Gmach ***@***.***> wrote:
I tried to come up with a test for...
https://github.com/koodaamo/tnefparse/blob/d29d976e58c4faab789e6a47f726334b442a727a/tnefparse/util.py#L41-L47
I even wrote a helper to iterate over date/time ranges, but I found no value which fails for the try block and succeeds for the except block.
The change was introduced in be35566
@Beercow @petri Maybe you know or remember why this try/except statement was introduced in the first place?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hi @Beercow thank you very much for getting back to me. As you seem to have some more domain knowledge in this topic, could you give me a microsecond number which is too large, but fits the condition in the except branch?
As I wrote above, I did not find a number on my own. Here is the complete code snippet: Lines 41 to 47 in f81554d
|
Maybe this is simply to overcome the fact that the max for python timestamps and dates is different? https://stackoverflow.com/questions/39153700/why-cant-pythons-datetime-max-survive-a-round-trip-through-timestamp-fromtim |
Unfortunately, I do not have the file I was working with anymore. Trying to find one that brings up the error. |
While test coverage is already at a very good 93%, the PR #84 alone would have brought two regressions (changed log level + no more help text), as there are still some lines without coverage.
I suggest to fill the coverage gaps before continuing to work on the current open PRs.
The text was updated successfully, but these errors were encountered: