Noisy wall of "Perhaps you already have a cluster running?" warnings when running pytest #510
Labels
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
sprint
A good issue to tackle during a sprint
Comments
|
I think that @fjetter is solving this in
dask/distributed#4928
…On Thu, Jul 22, 2021 at 1:24 AM Loïc Estève ***@***.***> wrote:
This is annoying because you need to scroll up a lot to look at the actual
useful output. There is probably a way either to catch these warnings with
pytest or to ignore them at the end of the report.
pytest dask_jobqueue
Part of the output at the end of the run:
dask_jobqueue/tests/test_pbs.py::test_job_script[PBSCluster]
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 33339 instead
warnings.warn(
dask_jobqueue/tests/test_pbs.py::test_job_script[MoabCluster]
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 40255 instead
warnings.warn(
dask_jobqueue/tests/test_pbs.py::test_job_script[MoabCluster]
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 41619 instead
warnings.warn(
dask_jobqueue/tests/test_pbs.py::test_config
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 45387 instead
warnings.warn(
dask_jobqueue/tests/test_pbs.py::test_config_name_pbs_takes_custom_config
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 36611 instead
warnings.warn(
dask_jobqueue/tests/test_pbs.py::test_adapt
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 34711 instead
warnings.warn(
dask_jobqueue/tests/test_sge.py::test_config_name_sge_takes_custom_config
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 35511 instead
warnings.warn(
dask_jobqueue/tests/test_sge.py::test_job_script
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 42161 instead
warnings.warn(
dask_jobqueue/tests/test_slurm.py::test_header
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 34657 instead
warnings.warn(
dask_jobqueue/tests/test_slurm.py::test_header
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 33211 instead
warnings.warn(
dask_jobqueue/tests/test_slurm.py::test_header
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 33897 instead
warnings.warn(
dask_jobqueue/tests/test_slurm.py::test_job_script
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 39487 instead
warnings.warn(
dask_jobqueue/tests/test_slurm.py::test_job_script
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 42561 instead
warnings.warn(
dask_jobqueue/tests/test_slurm.py::test_config_name_slurm_takes_custom_config
/home/lesteve/miniconda3/lib/python3.9/site-packages/distributed/node.py:160: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 43363 instead
warnings.warn(
-- Docs: https://docs.pytest.org/en/stable/warnings.html
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#510>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTAJGOU2SRBJRXPRKOTTY62STANCNFSM5AZLCQDA>
.
|
|
Ah nice, thanks for letting me know! I guess we can live with it a bit longer and wait for a proper solution in distributed then! |
If it becomes unbearable, a |
|
I'm closing this one as a fix should be soon available in distributed, we can live with it for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is annoying because you need to scroll up a lot to look at the actual useful output. There is probably a way either to catch these warnings with pytest or to ignore them at the end of the report.
Part of the output at the end of the run:
The text was updated successfully, but these errors were encountered: