Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Test failed on Debian armel

Open
  • Is something wrong?
#72 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
testing-qa

Research direction

Start with tests/test_integration_tox4.py::test_allenvs_print_extras_to_file and compare the captured Debian armel output with prep_tox_output and the expected environment order. Reproduce the failure using the linked autopkgtest log or the project test suite; done means this parameterized test passes without breaking the other output checks.

Written by the indexing model from the issue text.

Description

help wanted

Hi,

I have packaged the module for Debian, but there is one test case failed that stopping the package migration to testing from sid.

The specilly log is here

 56s 4.11.3 from /usr/lib/python3/dist-packages/tox/__init__.py
 56s registered plugins:
 56s     tox-current-env-0.0.11 at /usr/lib/python3/dist-packages/tox_current_env/hooks.py
 56s 
 56s 
 56s 
 56s 
 56s =================================== FAILURES ===================================
 56s __________ test_allenvs_print_extras_to_file[--print-extras-to-file] ___________
 56s [gw6] linux -- Python 3.11.6 /usr/bin/python3.11
 56s 
 56s tmp_path = PosixPath('/tmp/pytest-of-debci/pytest-0/popen-gw6/test_allenvs_print_extras_to_f0')
 56s option = '--print-extras-to-file'
 56s 
 56s     @pytest.mark.parametrize("option", ("--print-extras-to", "--print-extras-to-file"))
 56s     def test_allenvs_print_extras_to_file(tmp_path, option):
 56s         extraspath = tmp_path / "extras"
 56s         result = tox(option, str(extraspath))
 56s         assert sorted(extraspath.read_text().splitlines()) == sorted(
 56s             ["dev", "full"] * len(envs_from_tox_ini())
 56s         )
 56s         expected = ""
 56s         for env in envs_from_tox_ini()[:-1]:
 56s             expected += f"{env}: OK\n"
 56s         expected += tox_footer(spaces=0) + "\n"
 56s >       assert prep_tox_output(result.stdout) == expected
 56s E       AssertionError: assert 'py36: OK\npy...ulations :)\n' == 'py36: OK\npy...ulations :)\n'
 56s E           py36: OK
 56s E           py37: OK
 56s E           py38: OK
 56s E         + py310: OK
 56s E           py39: OK
 56s E         - py310: OK
 56s E             py36: OK...
 56s E         
 56s E         ...Full output truncated (6 lines hidden), use '-vv' to show
 56s 
 56s /tmp/autopkgtest-lxc.4a3lx05w/downtmp/autopkgtest_tmp/tests/test_integration_tox4.py:231: AssertionError
 56s ----------------------------- Captured stdout call -----------------------------
 56s current /tmp/pytest-of-debci/pytest-0/popen-gw6/test_allenvs_print_extras_to_f0/projdir running in /tmp/pytest-of-debci/pytest-0/popen-gw6/test_allenvs_print_extras_to_f0/projdir
 56s py36: OK ✔ in 0.01 seconds
 56s py37: OK ✔ in 0.02 seconds
 56s py38: OK ✔ in 0.01 seconds
 56s py310: OK ✔ in 0.01 seconds
 56s py39: OK ✔ in 0.01 seconds
 56s   py36: OK (0.01 seconds)
 56s   py37: OK (0.02 seconds)
 56s   py38: OK (0.00 seconds)
 56s   py39: OK (0.00 seconds)
 56s   py310: OK (0.00 seconds)
 56s   py311: OK (0.01 seconds)
 56s   congratulations :) (0.13 seconds)
 56s 
 56s ----------------------------- Captured stderr call -----------------------------
 56s 
 56s =========================== short test summary info ============================
 56s FAILED tests/test_integration_tox4.py::test_allenvs_print_extras_to_file[--print-extras-to-file]

The more test results you can refer to tracker
any help will be appreciated.

Dominant language
Python
Stars
26
Forks
9
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from fedora-python/tox-current-env

All issues in fedora-python/tox-current-env

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.