jaraco / jaraco/cmdix

Tests crash on pypy

Open
#11 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted
Dominant language
Python
Stars
30
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Here's output from a recent run:

  tox
  shell: /usr/bin/bash -e {0}
  env:
    pythonLocation: /opt/hostedtoolcache/PyPy/3.9.12/x64
    Python_ROOT_DIR: /opt/hostedtoolcache/PyPy/3.9.12/x64
    Python2_ROOT_DIR: /opt/hostedtoolcache/PyPy/3.9.12/x64
    Python3_ROOT_DIR: /opt/hostedtoolcache/PyPy/3.9.12/x64
    PKG_CONFIG_PATH: /opt/hostedtoolcache/PyPy/3.9.12/x64/bin/lib/pkgconfig
python create: /home/runner/work/cmdix/cmdix/.tox/python
python installdeps: pytest >= 6.2.1
python develop-inst: /home/runner/work/cmdix/cmdix
ERROR: invocation failed (exit code -9), logfile: /home/runner/work/cmdix/cmdix/.tox/python/log/python-3.log
================================== log start ===================================

=================================== log end ====================================
___________________________________ summary ____________________________________
ERROR:   python: InvocationError for command /home/runner/work/cmdix/cmdix/.tox/python/bin/python -m pip freeze (exited with code -9 (SIGKILL)) (exited with code -9)

The process doesn't always fail precisely that way. Here's output from an earlier run:

  tox
  shell: /usr/bin/bash -e {0}
  env:
    pythonLocation: /opt/hostedtoolcache/PyPy/3.9.12/x64
    Python_ROOT_DIR: /opt/hostedtoolcache/PyPy/3.9.12/x64
    Python2_ROOT_DIR: /opt/hostedtoolcache/PyPy/3.9.12/x64
    Python3_ROOT_DIR: /opt/hostedtoolcache/PyPy/3.9.12/x64
    PKG_CONFIG_PATH: /opt/hostedtoolcache/PyPy/3.9.12/x64/bin/lib/pkgconfig
python create: /home/runner/work/cmdix/cmdix/.tox/python
python installdeps: pytest >= 6.2.1
python develop-inst: /home/runner/work/cmdix/cmdix
/home/runner/work/_temp/8f22a1bd-6a25-45f6-9a61-1150bb55390b.sh: line 1:  1706 Killed                  tox
Error: Process completed with exit code 137.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the GitHub Actions run linked in the issue and the tox invocation that creates the PyPy environment. Reproduce the failure with the reported PyPy version, pytest dependency, and pip freeze step, then determine why the process is killed. Done means the test job completes successfully on PyPy without the reported SIGKILL or exit 137.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, python
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.