IPyWidget tests randomly fail
See original GitHub issueEnvironment data
- VS Code version: XXX
- Extension version (available under the Extensions sidebar): XXX
- Python Extension version (available under the Extensions sidebar): XXX
- OS (Windows | Mac | Linux distro) and version: XXX
- Python and/or Anaconda version: XXX
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): XXX
- Jupyter server running: Local | Remote | N/A
Expected behaviour
XXX
Actual behaviour
XXX
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
- XXX
Logs
Output for Python
in the Output
panel (View
→Output
, change the drop-down the upper-right of the Output
panel to Python
)
XXX
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
IPywidget error in Jlab 2.0 · Issue #2826 · jupyter-widgets ...
I have an ipywidgets extension that works on jlab 1.2.6 but getting ... JupyterLab 2 support jupyterlab-sidecar#38 (Needs test error fixed) ...
Read more >No module named 'ipywidgets' error when running IPyhon ...
ipywidgets is not installed with IPython. Just install it. pip install ipywidgets.
Read more >ipywidgets Documentation
Install ipywidgets in each kernel's environment that will use ipywidgets. For example, if using conda environments, with Jupyter Notebook ...
Read more >"Randomly" failing tests | Apple Developer Forums
We have a test suite that passes when tests are run manually via Xcode. But when run through Xcode Server on about 50...
Read more >Testing — Panel v0.14.1
This chapter describes how to run various tests locally in a development environment, guidelines for writing tests, and information regarding ...
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
Was just looking at this as part of investigating https://github.com/microsoft/vscode-jupyter/issues/3955. If I manually run the ipyvolume notebook, the first cell actually does take a fair bit of time to run, so I’m not surprised that we sometimes timeout waiting for the cell to execute. I noticed that at least for the ipyvolume test, we have retry logic for the part where we verify the outputs, but we don’t retry execution if that times out. I tried moving the cell execution into the retry for the ipyvolume test since that seems to be the one that times out the most often, if that helps and sounds like a good idea we can maybe consider doing this for the other tests.
Update: there are three failure types I have seen based on past GHA run logs:
Timeout after 3min: this is associated with a ‘Failed to load resource net::ERR_CONTENT_LENGTH_MISMATCH’ error. Not sure what the root cause of this is. Don had submitted a PR that we thought would fix this but it’s still cropping up. This is the most common failure case.
rendered_execution timeout. I cannot repro this yet. Just need to add more logging.
AttributeErrors in the output. That one as far as I can tell is the CDN not responding with the script source. This is the least common failure and also the one we can do the least about.