Tox in verbose mode?

Open
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, python
Domain
ci-cd

Research direction

Start by reviewing how the action and container handle TOX_PARAMS, then compare the default installation output with the -vvvvv behavior described in the issue. Clarify whether verbosity belongs in the action or container configuration, and consider the user override mentioned in the report. Done means the installation process provides the requested diagnostic detail without preventing user settings from overriding it.

Written by the indexing model from the issue text.

Description

It might be useful to have tox in more verbose mode than the default. I'm gonna explain what happened to me recently. I've prepared a CI job with fedora-python-tox. The test dependencies contain one which has to be compiled from sources and therefore needs some non-Python deps to be installed in the container in advance. If the system package is missing, pip fails to install (compile) the package, and instead of exiting with an error, it keeps trying with older and older versions of the same package all failing for the same reason. This ended up after hours because of timeout. To uncover the problem, I had to manually add

      env:
        TOX_PARAMS: -vvvvv

to the config to see what's happening during the installation process.

I know that the verbose mode might produce a lot of logs but having a log of the installation process sounds reasonable to me. What do you think? Should this be done on the action or container image level? I believe that both can be overwritten by user settings.

Dominant language
Python
Stars
17
Forks
3
No merged PRs in 30d

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.

More from fedora-python/tox-github-action

All issues in fedora-python/tox-github-action

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.