Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Tox in verbose mode?

未关闭
#17 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
github-actions, python
领域
ci-cd

调研方向

首先检查 action 和容器如何处理 TOX_PARAMS,然后将默认安装输出与 issue 中描述的 -vvvvv 行为进行比较。明确详细程度应属于 action 还是容器配置,并考虑报告中提到的用户覆盖设置。当安装过程提供所请求的诊断详细信息,同时不阻止用户设置覆盖该详细程度时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Python
星标
17
派生
3
PR 合并指标
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

fedora-python/tox-github-action 的其他 Issue

查看 fedora-python/tox-github-action 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。