Easier debugging ideas
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, github, shell
- Domain
- ci-cd, devops, infrastructure, testing
Research direction
No file or test entry point is named. Start by surveying the test setup and GitHub comment handling, then narrow the four debugging ideas to an agreed scope; done should include an explicit implementation plan and validation for the selected behavior.
Written by the indexing model from the issue text.
Description
Brain dump of some ideas how to make the debugging easier:
- print docker/podman version at the beginning of the test (plus some other related packages)
- do some performance check at the beginning (how quickly network works by pulling some small image and installing a package; how quickly a container starts) -- seeing bigger numbers might indicate that the issues are caused by infra performance
- add possibility to not dispose a machine immediately -- some message like
[keep-alive: 2h]in the github comment could make the machine be kept a little longer after the test is done (see https://plugins.jenkins.io/ghprb/ for how to work with the comments) - similarly as the point above
[debug]could turn on the debug (more verbose) output for the tests
- Dominant language
- Shell
- Stars
- 25
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 sclorg/container-common-scripts
-
sclorg/container-common-scripts#425 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sclorg/container-common-scripts#332 · 1 reaction ·
-
sclorg/container-common-scripts#264 · 1 assignee ·
All issues in sclorg/container-common-scripts
Similar issues
-
Update Vish to 1.1.5 Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 comment ·
-
help wanted new command
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tldr-pages/tldr#24151 ·
-
PacReq: Rune IDE Openpackage request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pacstall/pacstall-programs#9402 ·
-
[BUG] ci: the first prefetch-images.sh call runs before shard.txt exists, so it is always a no-op Openbug github-actions
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
update-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
msys2/MINGW-packages#31768 ·