benchopt / benchopt/benchmark_logreg_l2
Handle issues from other packages side?
- Dominant language
- Python
- Stars
- 5
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
The CI is currently red and one of the reasons is a problem from a package that is used (see ).
Technically, this is not a BenchOpt error, and it can impact multiple repositories if the same library is used for different problems to solve.
So where is the limit (if there is one) between a warning in the CI that there is a problem on some library side and a real error from BenchOpt that we can deal with?
(poke @josephsalmon)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked CI action test log at line 186 and identify whether the failure originates in BenchOpt or a dependency. Review how this benchmark reports CI failures, then define the boundary between dependency warnings and BenchOpt errors. Done means the handling and expected CI outcome are agreed and documented or implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100