-
Notifications
You must be signed in to change notification settings - Fork 39
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: wait longer after z_put #351
fix: wait longer after z_put #351
Conversation
PR missing one of the required labels: {'documentation', 'new feature', 'dependencies', 'breaking-change', 'internal', 'enhancement', 'bug'} |
06a4e53
to
b567c3d
Compare
b567c3d
to
2d23187
Compare
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'm not sure we need the fixture
dependency for that, but it doesn't really matter. Otherwise, LGTM
run: pip3 install pytest pytest-xdist | ||
run: pip3 install pytest pytest-xdist fixtures | ||
|
||
- name: Run examples check |
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.
Why do you need another step for examples check? Isn't it also executed as part of next pytest
command?
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.
It looks like the pytest step doesn't auto detect the tests in examples
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 could change the name of tests/examples_check.py
to tests/test_examples.py
and it would be picked up by the pytest step. Should the same be done for stubs_check.py
and have a single pytest call that calls all of them? Maybe having them in their own steps might be helpful for debugging. What do you think?
Attempt to fix racy behaviour in tests like: https://github.com/eclipse-zenoh/zenoh-python/actions/runs/11158739052/job/31015765836
This started as small fix to increase sleep times and ended up with a re-org of the examples test code.