-
Notifications
You must be signed in to change notification settings - Fork 16
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
When using RobotFramework-requestslibrary, sometimes the log will not generate #28
Comments
@ZIAME If you could author a test case that even randomly fails this way, please, share it here. |
I could not figure out any obvious reason for this behavior, so I am interested for examples and observations. |
I am actually looking at some that I cannot share. Once I reproduce in some neutral place, I will be sure to share again |
@ZIAME Sure. No hurry. What library was that exactly? https://pypi.org/search/?q=robotframework-requestslibrary gives no results. I did try https://pypi.org/project/robotframework-requests/ at https://mybinder.org/v2/gh/robots-from-jupyter/robotkernel/master and tried to run some of its tests multiple times without restarting the kernel, but was unable to reproduce this with them If you have not been using Binder before:
|
By " I can't share " I meant that I mustn't, not that I am not able. :) I will get back to you as soon as I can. It's very elusive, but when you have the "correct" set, it just stays bad 🍡 |
i am using robotkernel in jupyterlab Version 1.1.4.
i am also using robotframework-requestslibrary. for some reason - and only with this library - and only in jupyterlab/robotkernel -- I am getting this problem that cell with Test Case will not end.
It gets stuck with
and shows that it's still doing the last keyword in the test -- for example the suite teardown. Actual result is that everything has correctly finished, it's just the log that won't be generated.
when i run the test using nbrobot it ends correctly and with generated log.
Sadly it seems i cannot reliably get a logical conclusion on when this happens. I have a test with given words send in body and it works, when i change them to different words, it gets stuck:
Body: {message: "hello"} --> OK
Body: {message: "hi!"} --> stuck
Leaving it out here, maybe someone had a similar problem and found a solution :)
The text was updated successfully, but these errors were encountered: