-
Notifications
You must be signed in to change notification settings - Fork 94
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
Fix suite freeze on non-existent xtrigger - 7.8.x #3059
Fix suite freeze on non-existent xtrigger - 7.8.x #3059
Conversation
Travis is unhappy because of an error with
(this error appears near the top of the output, which is misleading, as you normally expect the error near the bottom of the file/output) |
I couldn't see that log detail at all, was just the working info.. anyways fixed. |
Given the final comments under #3056, do we need to raise a new PR against master for a test and back port that here? |
Happy to merge this otherwise, and have separate back port PR for test. |
Is that #3060? |
Yup, I merged it too quickly, sorry. So now we will have yet another backport pull request. Mea culpa 😞 I'll submit it once both get merged. |
Worked out well, since your test construction > mine ATM (>.<) ... Gave me a chance to use yours as a tutorial. |
raise SuiteConfigError("ERROR, xtrigger function " | ||
"not callable: " | ||
"%s" % xtrig.func_name) | ||
except ImportError: |
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.
Hmmm, just realized you have ModuleNotFoundError
on master
, and the parent class ImportError
on 7.8.x
. I think we better use the parent ImportError
on master too @dwsutherland . WDYT?
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.
@kinow - Yes, as python3 gave me ModuleNotFoundError
, but python2 produced ImportError
and the former is not recognised. I didn't try ImportError
in python3 (Is it back compat?), and figured both have diverged anyway.. Is this ok?
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.
Interesting (another hole in my Python 3 knowledge!).
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.
I believe ImportError
is the parent class of ModuleNotFoundError
.
Interesting (another hole in my Python 3 knowledge!).
Me too! I thought at least this part was consistent in both. But catching the parent class should be fine, though better to confirm if that works. Perhaps the unit tests could be used to validate that it works?
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.
I believe
ImportError
is the parent class ofModuleNotFoundError
.
Well I guess the child doesn't exist in python2 ... Consistency aside, would it have been better to use the parent?
Also does consistency matter between 7.8.x and 8? at some point we'll stop back porting changes? (as I guess it matters for that)
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.
Good point. If that works as-is, all good then I think
Port of pull/3056