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
- 46
- Avg merge
- 25d 1h
- 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 sclorg/container-common-scripts
-
Update Dockerfile.rhel11 base image from ubi10 to ubi11 once ubi11 images are availableMay be free again @hhorak claimed this 173 days ago, and no pull request is open. Open
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 ·
-
Add test also for OpenShift use cases.May be free again @phracek claimed this 747 days ago, and no pull request is open. Open
sclorg/container-common-scripts#264 · 1 assignee ·
All issues in sclorg/container-common-scripts
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area/tests theme/ci-dx
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
[Bug]: e2e script flag parsing is brokenPossibly taken @ericcurtin claimed this today. Openarea/dev-infra area/tests kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
agent-substrate/substrate#2217 · 1 comment ·
Maintainers usually reply within 1 day
-
Update "Making Changes to an Existing Competition" section in Delegate Handbook to align with WCRPOpen
Difficulty 1/5 Under an hour Newbie friendliness 74/100
thewca/wca-documents#613 ·