Remove pytest warnings capturing to reduce log verbosity
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system, ci-cd
Research direction
Start with the pytest configuration in pyproject.toml and inspect how cibuildwheel runs the wheel tests, comparing that setup with the main repository configuration. Remove the warning-capturing option from the relevant wheel-build test configuration, then verify that the CI log is less verbose without breaking the wheel tests.
Written by the indexing model from the issue text.
Description
This makes the CI log unecessarily verbose and pain to navigate. We do it in the main repo in pyproject.toml but I guess this is not taken into account because of how cibuildwheel tests are run.
[tool.pytest.ini_options]
doctest_optionflags = "NORMALIZE_WHITESPACE ELLIPSIS"
testpaths = "sklearn"
addopts = [
"--disable-pytest-warnings",
"--color=yes",
"--import-mode=importlib",
]
Note: this also happens for wheels builds in scikit-learn repo. I just haven't been annoyed about it enough until today.
- Dominant language
- Shell
- Stars
- 2
- Forks
- 4
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 1
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from scikit-learn/scikit-learn-release
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Copy check_version from numpy to make sure we build from a tag when we upload to PyPIPossibly taken @jeremiedbb claimed this 33 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
scikit-learn/scikit-learn-release#15 · 1 comment ·
-
Create a release branch in the scikit-learn-release repo matching the name of the scikit-learn repoOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
scikit-learn/scikit-learn-release#12 · 1 comment ·
-
Remove chain input from wheels.yml?Possibly taken @jeremiedbb claimed this 33 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
scikit-learn/scikit-learn-release#14 · 2 comments ·
-
Add `SOURCE_REF_TO_BUILD` rather than manual input field?Possibly taken @jeremiedbb claimed this 33 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
scikit-learn/scikit-learn-release#13 · 2 comments ·
All issues in scikit-learn/scikit-learn-release
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 2 days
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
mattpocock/skills#1307 ·
Maintainers usually reply within 1 day
-
status: ready
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
melodic-software/claude-code-plugins#8537 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
vladmandic/sdnext#5161 ·
Maintainers usually reply within 1 day
-
severity: low
Difficulty 1/5 1-3 hours Newbie friendliness 89/100
luainkernel/lunatik#1980 ·
Maintainers usually reply within 1 day