[Bug] `test_cli.py` might not run in the master
See original GitHub issueSearch before asking
- I searched the issues and found no similar issues.
Ray Component
Ray Core
What happened + What you expected to happen
This line of code fails the test in the master because await
is not called within test_address
. But in the master CI, this failure seems to be not caught, meaning the test is probably not running in the master.
cc @jiaodong
Versions / Dependencies
N/A
Reproduction script
N/A
Anything else
No response
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
schemathesis/test_commands.py at master - GitHub
Run thousands of randomly generated test scenarios based on your API specification and always be sure your API works as expected.
Read more >New Python test.bisect tool - Victor Stinner blog 3
If tests still fail, use the subset as the new set. Otherwise, throw the subset. Loop until the subset is small enough or...
Read more >Use ExUnit to test CLI Elixir script - Stack Overflow
When the program waits for input at stin the ExUnit tests do not complete until I press Ctrl+D (end of input). I would...
Read more >Cisco Bug: CSCvr46885 - Cisco IOS Software for Cisco ...
Symptom: A vulnerability in one of the diagnostic test CLI commands of Cisco IOS Software for Cisco 800 Series Industrial ISRs and Cisco ......
Read more >vuepy · PyPI
vue.py provides Python bindings for Vue.js. It uses brython to run Python in the browser. Here is a simple example of an vue.py...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sure, no rush 😃 I will put up a PR to remove it anyways as it seems to be included by mistake.
Highly likely related to the version of
pytest-asyncio
I think… good to know it wasn’t broken in the master