Skip to content

Process hang with Coverage 6.3 #1310

Closed
cleanlab/cleanlab
#262

Description

@tunetheweb

Describe the bug
A clear and concise description of the bug.

We've been having issues with our CI in GitHub Actions for the last few hours, and think it might be because of Coverage 6.3 - it's the one thing that's changed, and freezing it at 6.2 seems to allow runs to complete successfully.

To Reproduce
How can we reproduce the problem? Please be specific. Don't link to a failing CI job. Answer the questions below:

  1. What version of Python are you using? 3.7 seems to be a bit buggy with this. We also run 3.8 - 3.10 in CI and no issues seen with that.
  2. What version of coverage.py shows the problem? The output of coverage debug sys is helpful. 6.2.3
  3. What versions of what packages do you have installed? The output of pip freeze is helpful. See https://gist.github.com/tunetheweb/4d288ea4467ba74a66b3a0e2e8d5e4ea
  4. What code shows the problem? Give us a specific commit of a specific repo that we can check out. If you've already worked around the problem, please provide a commit before that fix. This is tricky. We run a lot of commands in CI, but checking out https://github.com/sqlfluff/sqlfluff/ and running tox -e py37 -- -n 2 test should reproduce it. Having problems setting up a 3.7 environment but will try to get a better test case. We do use a multithreaded process and noticed some changes to that.
  5. What commands did you run?

Expected behavior
A clear and concise description of what you expected to happen.

Additional context
Add any other context about the problem here.

Will try to get a better repo.

Activity

  1. vEpiphyte commented on Jan 25, 2022

    @vEpiphyte

    We've experienced a similar issue with CI timeouts in CircleCI when using Python 3.8.
    This occurs when using pytest as our test runner with coverage.
    The hang occurs after tests pass and the coverage is reported to the console; it's almost like the python process fails to exit.

    (venv) root@af00fef01e49:/home/circleci/repo# python -V
    Python 3.8.12
    
    (venv) root@af00fef01e49:/home/circleci/repo# coverage debug sys
    -- sys -------------------------------------------------------
                   coverage_version: 6.3
                    coverage_module: /home/circleci/repo/venv/lib/python3.8/site-packages/coverage/__init__.py
                             tracer: -none-
                            CTracer: available
               plugins.file_tracers: -none-
                plugins.configurers: -none-
          plugins.context_switchers: -none-
                  configs_attempted: .coveragerc
                       configs_read: /home/circleci/repo/.coveragerc
                        config_file: /home/circleci/repo/.coveragerc
                    config_contents: b'[report]\nomit =\n    */synapse/tests/test_*\n'
                          data_file: -none-
                             python: 3.8.12 (default, Aug 31 2021, 16:30:39) [GCC 9.3.0]
                           platform: Linux-5.11.0-1022-aws-x86_64-with-glibc2.29
                     implementation: CPython
                         executable: /home/circleci/repo/venv/bin/python3
                       def_encoding: utf-8
                        fs_encoding: utf-8
                                pid: 322
                                cwd: /home/circleci/repo
                               path: /home/circleci/repo/venv/bin
                                     /home/circleci/.pyenv/versions/3.8.12/lib/python38.zip
                                     /home/circleci/.pyenv/versions/3.8.12/lib/python3.8
                                     /home/circleci/.pyenv/versions/3.8.12/lib/python3.8/lib-dynload
                                     /home/circleci/repo/venv/lib/python3.8/site-packages
                                     /home/circleci/repo
                        environment: HOME = /root
                       command_line: /home/circleci/repo/venv/bin/coverage debug sys
                    sqlite3_version: 2.6.0
             sqlite3_sqlite_version: 3.31.1
                 sqlite3_temp_store: 0
            sqlite3_compile_options: COMPILER=gcc-9.3.0; ENABLE_COLUMN_METADATA; ENABLE_DBSTAT_VTAB
                                     ENABLE_FTS3; ENABLE_FTS3_PARENTHESIS; ENABLE_FTS3_TOKENIZER
                                     ENABLE_FTS4; ENABLE_FTS5; ENABLE_JSON1
                                     ENABLE_LOAD_EXTENSION; ENABLE_PREUPDATE_HOOK; ENABLE_RTREE
                                     ENABLE_SESSION; ENABLE_STMTVTAB; ENABLE_UNLOCK_NOTIFY
                                     ENABLE_UPDATE_DELETE_LIMIT; HAVE_ISNAN; LIKE_DOESNT_MATCH_BLOBS
                                     MAX_SCHEMA_RETRY=25; MAX_VARIABLE_NUMBER=250000; OMIT_LOOKASIDE
                                     SECURE_DELETE; SOUNDEX; TEMP_STORE=1
                                     THREADSAFE=1; USE_URI
    

    Pip freeze output

    (venv) root@af00fef01e49:/home/circleci/repo# pip freeze
    aiohttp==3.8.1
    aiohttp-socks==0.6.1
    aioimaplib==0.9.0
    aiosignal==1.2.0
    aiosmtplib==1.1.6
    antlr4-python3-runtime==4.8
    appdirs==1.4.4
    arrow==1.2.1
    async-timeout==4.0.2
    attrs==21.4.0
    base58==2.1.1
    bech32==1.2.0
    cattrs==1.10.0
    cbor2==5.4.2
    certifi==2021.10.8
    cffi==1.15.0
    charset-normalizer==2.0.10
    colorama==0.4.4
    coverage==6.3
    cpe==1.2.1
    cryptography==36.0.1
    fastjsonschema==2.14.5
    fqdn==1.5.1
    frozenlist==1.3.0
    idna==3.3
    importlib-resources==5.4.0
    iniconfig==1.1.1
    isoduration==20.11.0
    jsonpointer==2.2
    jsonschema==4.4.0
    lark-parser==0.11.2
    lmdb==1.3.0
    more-itertools==8.12.0
    msgpack==1.0.3
    multidict==6.0.2
    oauthlib==3.1.1
    packaging==20.9
    pluggy==1.0.0
    prompt-toolkit==3.0.24
    py==1.11.0
    pycodestyle==2.8.0
    pycparser==2.21
    pycryptodome==3.12.0
    Pygments==2.7.4
    pyOpenSSL==21.0.0
    pyparsing==3.0.7
    pyrsistent==0.18.1
    pytest==6.2.5
    pytest-cov==3.0.0
    python-bitcoinlib==0.11.0
    python-dateutil==2.8.2
    python-socks==1.2.4
    PyYAML==6.0
    regex==2022.1.18
    requests==2.27.1
    requests-cache==0.9.1
    rfc3339-validator==0.1.4
    rfc3986-validator==0.1.1
    scalecodec==1.0.2
    simplejson==3.17.6
    six==1.16.0
    stix2-patterns==1.3.2
    stix2-validator==3.0.2
    -e git+ssh://[email protected]/vertexproject/synapse.git@c8568da02165fe0c8131b8ffcc1e48e20dc2ad07#egg=synapse
    toml==0.10.2
    tomli==2.0.0
    tornado==6.1
    typing_extensions==4.0.1
    uri-template==1.1.0
    url-normalize==1.4.3
    urllib3==1.26.8
    vcrpy==4.1.1
    wcwidth==0.2.5
    webcolors==1.11.1
    wrapt==1.13.3
    xxhash==2.0.2
    yarl==1.7.2
    zipp==3.7.0
    

    This happened to our master commit here
    vertexproject/synapse@1b2d327

    This was fixed in https://github.com/vertexproject/synapse/pull/2534/files#diff-c9c796259f3852b51b531b79cbf07820145088d4f108fb006ab44b15f0b15934R8

    We did find the following line in a CI log for one of the failing tests which may or may not be related - it occurred prior to the pytest warnings summary and the console coverage output.

    /home/circleci/repo/venv/lib/python3.8/site-packages/coverage/data.py:129: 
    CoverageWarning: Data file '/home/circleci/repo/.coverage.803d4f93f49b.429.890315' doesn't seem to be a coverage data file: cannot unpack non-iterable NoneType object
    
  2. tunetheweb commented on Jan 25, 2022

    @tunetheweb
    Author

    Interesting that you saw this on 3.8. We experienced some intermittent hanging in other Python versions but repeated hanging (every time) in 3.7, so wasn’t sure if the intermittent issues were related.

    I also forgot to include my error message. It happened near the end of the test, but not quite at the end as you experienced (not sqlfluff is our project, but the last line might be useful):

    [gw1] [ 90%] PASSED test/rules/yaml_test_cases_test.py::test__rule_test_global_config /home/runner/work/sqlfluff/sqlfluff/.tox/py37/lib/python3.7/site-packages/coverage/inorout.py:535: CoverageWarning: Module sqlfluff was previously imported, but not measured (module-not-measured)
    5583
      self.warn(msg, slug="module-not-measured")
    
  3. nedbat commented on Jan 26, 2022

    @nedbat
    Member

    I'm not clear what problems you are reporting. @tunetheweb the original issue description doesn't mention what the actual problem is. @vEpiphyte says they've seen similar problems, and mentions hanging. Then @tunetheweb shows a module-not-measured warning. This sounds like two different issues.

    Anything you can do to give me a reproducible scenario would be great.

  4. tunetheweb commented on Jan 26, 2022

    @tunetheweb
    Author

    Yes I appreciate this is a very poor issue to raise. Sorry about that, but thought I'd give you a heads up as saw it right after the release, and it stopped happening right after I pinned to the old version.

    Will try to give a more meaningful reproducible use case if I can narrow it down.

    The issue is jobs hanging (I cancelled them after an hour, when they normally take 5 mins. One job I left running and it took 3 hours and counting). That was for Python 3.7.
    I also saw a lot of slow down in jobs (5 min jobs were more often than not taking 20mins when they did complete). That was for Python 3.8+.

    Initially I thought GitHub Actions were on the blink but at soon as I pinned the old version of coverage it all worked. Unpinning it again breaks it again. Nothing else changes between the runs.

    But as to narrowing it down why, at the moment I don't have more info to help explain that. But will keep digging...

    Think the error message is a red-herring. It was the last thing printed before it froze. But do see that at the end of the run elsewhere (though interestingly I only see it at the end of good runs, whereas that appeared after our CI job was only at 90% and then hung).

    Sorry, again for such a poor report. Can close it if you want until I can get you more info, as appreciate it's difficult to do anything with what I've written here but as I say this was more a heads up, and a vague hope someone would have an idea what it might be 😞

  5. nedbat commented on Jan 26, 2022

    @nedbat
    Member

    @tunetheweb @vEpiphyte @sir-sigurd Can you try installing this branch of coverage.py to see if it fixes the problem?

    pip install git+https://github.com/nedbat/coveragepy@nedbat/fix-1312
    
  6. tunetheweb commented on Jan 26, 2022

    @tunetheweb
    Author

    Doesn't look any better with that to be honest.

    BTW happy to move this discussion to #1312 as that issue would appear to be a duplicate of this one, but with much better detail!

  7. tunetheweb commented on Jan 26, 2022

    @tunetheweb
    Author

    Yeah definitely seeing same issue with that unfortunately :-(

    But it is very reproducible so, while I haven't been able to help with a minimal reproducible test case, I'm very happy to test any other test branches you have. Just takes about 10mins to run.

  8. sir-sigurd commented on Jan 26, 2022

    @sir-sigurd

    @tunetheweb @vEpiphyte @sir-sigurd Can you try installing this branch of coverage.py to see if it fixes the problem?

    pip install git+https://github.com/nedbat/coveragepy@nedbat/fix-1312
    

    Nope, it doesn't help.

  9. vEpiphyte commented on Jan 26, 2022

    @vEpiphyte

    I did reproduce the error locally with a set of our unit tests. Recording this big blob for posterity - I haven't had the time to whittle it down yet but will do shortly.

    $ python -m pytest  -v -s -rs --durations 6 --maxfail 6 -p no:logging --junitxml=test-reports/junit.xml --cov synapse --no-cov-on-fail synapse/tests/test_cmds_trigger.py synapse/tests/test_lib_cell.py synapse/tests/test_lib_crypto_ecc.py synapse/tests/test_lib_hashset.py synapse/tests/test_lib_layer.py synapse/tests/test_lib_node.py synapse/tests/test_lib_scope.py synapse/tests/test_lib_stormhttp.py synapse/tests/test_lib_stormlib_model.py synapse/tests/test_lib_stormlib_yaml.py synapse/tests/test_lib_trigger.py synapse/tests/test_model_auth.py synapse/tests/test_model_geospace.py synapse/tests/test_model_media.py synapse/tests/test_servers_axon.py synapse/tests/test_tools_backup.py synapse/tests/test_tools_guid.py synapse/tests/test_tools_storm.py
    

    This produces the same hang locally using Python 3.8.10 on linux (ubuntu 21.04) and coverage 6.3.0.

    I then installed ned's patch with the following

    pip install git+https://github.com/nedbat/coveragepy@nedbat/fix-1312
    

    And got the same hang. Sending sigint (ctrl+c) to the process yielded the following traceback

    ^CError in atexit._run_exitfuncs:
    Traceback (most recent call last):
      File "/home/user/.pyenv/versions/3.8.10/lib/python3.8/multiprocessing/popen_fork.py", line 27, in poll
    Process SpawnProcess-22:
    Process SpawnProcess-18:
        pid, sts = os.waitpid(self.pid, flag)
    KeyboardInterrupt
    Traceback (most recent call last):
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 1096, in execute
        return self.con.execute(sql, parameters)
    Traceback (most recent call last):
    sqlite3.OperationalError: no such table: coverage_schema
    
    During handling of the above exception, another exception occurred:
    
    Traceback (most recent call last):
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 1101, in execute
        return self.con.execute(sql, parameters)
    sqlite3.OperationalError: no such table: coverage_schema
    
    The above exception was the direct cause of the following exception:
    
    Traceback (most recent call last):
      File "/home/user/.pyenv/versions/3.8.10/lib/python3.8/multiprocessing/process.py", line 318, in _bootstrap
        util._exit_function()
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 270, in _read_db
        schema_version, = db.execute_one("select version from coverage_schema")
      File "/home/user/.pyenv/versions/3.8.10/lib/python3.8/multiprocessing/util.py", line 334, in _exit_function
        _run_finalizers(0)
      File "/home/user/.pyenv/versions/3.8.10/lib/python3.8/multiprocessing/util.py", line 300, in _run_finalizers
        finalizer()
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 1129, in execute_one
        rows = list(self.execute(sql, parameters))
      File "/home/user/.pyenv/versions/3.8.10/lib/python3.8/multiprocessing/util.py", line 224, in __call__
        res = self._callback(*self._args, **self._kwargs)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/pytest_cov/embed.py", line 99, in cleanup
        _cleanup(_active_cov)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 1118, in execute
        raise DataError(f"Couldn't use data file {self.filename!r}: {msg}") from exc
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/pytest_cov/embed.py", line 84, in _cleanup
        cov.stop()
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/control.py", line 700, in save
        data = self.get_data()
    coverage.exceptions.DataError: Couldn't use data file '/home/user/PycharmProjects/synapse/.coverage.vertex005c.35596.883395': no such table: coverage_schema
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/control.py", line 769, in get_data
        if self._collector and self._collector.flush_data():
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/collector.py", line 473, in flush_data
        self.covdata.add_lines(self.mapped_file_dict(self.data))
    
    During handling of the above exception, another exception occurred:
    
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 236, in _wrapped
        return method(self, *args, **kwargs)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 466, in add_lines
        file_id = self._file_id(filename, add=True)
    Traceback (most recent call last):
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 388, in _file_id
        cur = con.execute("insert or replace into file (path) values (?)", (filename,))
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 1096, in execute
        return self.con.execute(sql, parameters)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/control.py", line 608, in _on_sigterm
        self._atexit("sigterm")
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/control.py", line 604, in _atexit
        self.save()
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/control.py", line 700, in save
        data = self.get_data()
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/control.py", line 769, in get_data
        if self._collector and self._collector.flush_data():
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/collector.py", line 473, in flush_data
        self.covdata.add_lines(self.mapped_file_dict(self.data))
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 234, in _wrapped
        with self._lock:
      File "/home/user/.pyenv/versions/3.8.10/lib/python3.8/multiprocessing/process.py", line 318, in _bootstrap
        util._exit_function()
    KeyboardInterrupt
      File "/home/user/.pyenv/versions/3.8.10/lib/python3.8/multiprocessing/util.py", line 334, in _exit_function
        _run_finalizers(0)
      File "/home/user/.pyenv/versions/3.8.10/lib/python3.8/multiprocessing/util.py", line 300, in _run_finalizers
        finalizer()
      File "/home/user/.pyenv/versions/3.8.10/lib/python3.8/multiprocessing/util.py", line 224, in __call__
        res = self._callback(*self._args, **self._kwargs)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/pytest_cov/embed.py", line 99, in cleanup
        _cleanup(_active_cov)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/pytest_cov/embed.py", line 84, in _cleanup
        cov.stop()
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/control.py", line 700, in save
        data = self.get_data()
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/control.py", line 769, in get_data
        if self._collector and self._collector.flush_data():
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/collector.py", line 473, in flush_data
        self.covdata.add_lines(self.mapped_file_dict(self.data))
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 236, in _wrapped
        return method(self, *args, **kwargs)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 459, in add_lines
        self._choose_lines_or_arcs(lines=True)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 518, in _choose_lines_or_arcs
        with self._connect() as con:
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 313, in _connect
        self._open_db()
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 264, in _open_db
        self._read_db()
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 273, in _read_db
        self._init_db(db)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 299, in _init_db
        db.executescript(SCHEMA)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 1156, in executescript
        self.con.executescript(script)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/control.py", line 608, in _on_sigterm
        self._atexit("sigterm")
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/control.py", line 604, in _atexit
        self.save()
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/control.py", line 700, in save
        data = self.get_data()
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/control.py", line 769, in get_data
        if self._collector and self._collector.flush_data():
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/collector.py", line 473, in flush_data
        self.covdata.add_lines(self.mapped_file_dict(self.data))
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 234, in _wrapped
        with self._lock:
    KeyboardInterrupt
    Error in atexit._run_exitfuncs:
    Traceback (most recent call last):
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 1096, in execute
        return self.con.execute(sql, parameters)
    sqlite3.OperationalError: no such table: context
    
    During handling of the above exception, another exception occurred:
    
    Traceback (most recent call last):
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 1101, in execute
        return self.con.execute(sql, parameters)
    sqlite3.OperationalError: no such table: context
    
    The above exception was the direct cause of the following exception:
    
    Traceback (most recent call last):
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 236, in _wrapped
        return method(self, *args, **kwargs)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 463, in add_lines
        self._set_context_id()
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 421, in _set_context_id
        context_id = self._context_id(context)
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 397, in _context_id
        row = con.execute_one("select id from context where context = ?", (context,))
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 1129, in execute_one
        rows = list(self.execute(sql, parameters))
      File "/home/user/.pyenv/versions/3.8.10/envs/syn3810/lib/python3.8/site-packages/coverage/sqldata.py", line 1118, in execute
        raise DataError(f"Couldn't use data file {self.filename!r}: {msg}") from exc
    coverage.exceptions.DataError: Couldn't use data file '/home/user/PycharmProjects/synapse/.coverage.vertex005c.35541.378922': no such table: context
    
  10. 90 remaining items

  11. asottile commented on May 18, 2022

    @asottile
    Contributor

    can confirm it works with my minimal reproduction above 🎉 (and again fails with [run] sigterm = true as expected!)

  12. tunetheweb commented on May 18, 2022

    @tunetheweb
    Author

    Can confirm I can see no issues with my pipeline with this branch either.

    Great to get this resolve so can unpin the version number on the next release. Thanks for your efforts!

  13. added a commit that references this issue on May 19, 2022
  14. nedbat commented on May 22, 2022

    @nedbat
    Member

    This is now released as part of coverage 6.4.

  15. johnthagen commented on May 23, 2022

    @johnthagen

    @nedbat I can confirm that Coverage 6.4 solved our multiprocessing.Pool deadlocks in CI.

    Thanks! ❤️

  16. pllim commented on May 23, 2022

    @pllim

    v6.4 works for me. Thanks!

  17. added a commit that references this issue on May 25, 2022
  18. added a commit that references this issue on Jun 14, 2022
  19. added a commit that references this issue on Aug 24, 2022
  20. added a commit that references this issue on May 11, 2026
  21. added a commit that references this issue on May 14, 2026
  22. added a commit that references this issue on Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions