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
threads.tmap() test and and fix. Unsurfaced bug #1768 #1965
Conversation
Looks like the same thing has happened in the travis build, which at least is good for reproducibility
|
I guess we need to resolve the issue with tmap before anything can be done with this unit test. |
Yeah, that's what I think. Should I switch this to a draft and make a new issue? |
Sounds sensible to me. |
@MyreMylar Here: #1985 |
Modified tmap per issue #1985 |
Cool. Are you intending to look at the unfinished unit test that starts with Lines 131 to 143 in 7d3900d
No worries if you are not. |
I actually hadn't noticed it and assumed that the main tmap test was the one that was unfinished. I wanted to add further tests to the main tmap test and I can have a look at the existing todo when I do that. |
I think we can merge this one in now. Further work on tmap tests can happen in other PRs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks :)
Issue: #1768
Background:
threads.tmap()
was missing unit tests, so I wrote a unit test to cover the situation where the optional parameterstop_on_error
is set toFalse
. The purpose ofstop_on_error
is to determine whethertmap
should return a result or throw an error if one or more of the function calls it makes throw exceptions.Description: As part of my unit test's setup, it calls
tmap
with thestop_on_error
flag set toFalse
. However, an exception is thrown bytmap
during this process because the resultingFuncResult
s don't have theresult
attribute they are expected to.Caveats: The actual form of the unit test may need to change depending on how the issue preventing it from running is resolved. It needs to be determined what the actual correct result should be in order to write the unit test.
Finally, this is the stack trace I got before.
This is my first PR to this project, so let me know if I have made mistakes in formatting it or if you need more information. Thanks!