Reduce messages in test output
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
- r
- Domain
- testing-qa
Research direction
Start by running test_check("extratests", reporter = "summary") and inspect the noisy output shown in the issue. Identify how package messages and repeated Gaussian process warnings appear during the test run; done means actual test failures are easy to spot without unrelated messages obscuring them.
Written by the indexing model from the issue text.
Description
The output for test failures is very noisy, making it hard to spot the actual failures amidst all the messages.
test_check("extratests", reporter = "summary")
parsnip-extension-messaging: ....Loading required package: survival
...................
S3-registration: ......
butcher-recipes:
Attaching package: 'Matrix'
The following objects are masked from 'package:tidyr':
expand, pack, unpack
....
encodings-glmnet: Loaded glmnet 4.1-8
.........
encodings-randomForest: ......
encodings-ranger: ......
engine-parameters-c5: ..! The Gaussian process model is being fit using 3 features but only has 3
data points to do so. This may cause errors or a poor model fit.
! The Gaussian process model is being fit using 3 features but only has 4
data points to do so. This may cause errors or a poor model fit.
....! The Gaussian process model is being fit using 3 features but only has 3
data points to do so. This may cause errors or a poor model fit.
! The Gaussian process model is being fit using 3 features but only has 4
data points to do so. This may cause errors or a poor model fit.
..
engine-parameters-earth: ..! The Gaussian process model is being fit using 2 features but only has 3
data points to do so. This may cause errors or a poor model fit.
..
- Dominant language
- R
- Stars
- 23
- Forks
- 0
- PR merge metrics
- 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
- 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 tidymodels/extratests
-
feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
tidymodels/extratests#303 ·
-
upkeep
Difficulty 4/5 3-5 days Newbie friendliness 25/100
tidymodels/extratests#270 ·
-
bug upkeep
Difficulty 4/5 3-5 days Newbie friendliness 35/100
tidymodels/extratests#254 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
tidymodels/extratests#253 ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
tidymodels/extratests#252 ·
All issues in tidymodels/extratests
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Bioconductor/BiocCheck#264 ·
-
Length 1 columns are written as scalarsPossibly taken @lazappi claimed this today. Openbug triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
easystats/parameters#1290 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
corybrunson/ordr#91 ·