Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow entering the container to debug its state #1032

Open
aleixpol opened this issue Nov 13, 2023 · 2 comments · May be fixed by #1460
Open

Allow entering the container to debug its state #1032

aleixpol opened this issue Nov 13, 2023 · 2 comments · May be fixed by #1460
Labels
nice Down prioritized

Comments

@aleixpol
Copy link

Is your feature request related to a problem? Please describe.
I am trying to debug a crash in a process using this tool. I'd need to run again one of the processes with gdb and interact with it.

Describe the solution you'd like
I'd like to be offered a way to interact with the system as one of the tests fails.

Describe alternatives you've considered
I looked into modifying our ci tooling to call the processes by default with gdb, can't really do that without breaking our current ci as we get the recipes from elsewhere shared.

Additional context
This is the CI in question:
https://invent.kde.org/plasma/kwin/-/blob/Plasma/5.27/.gitlab-ci.yml?ref_type=heads
@firecow firecow added the nice Down prioritized label Nov 21, 2023
@firecow
Copy link
Owner

firecow commented Nov 21, 2023 •
edited
Loading

You need to make a more precise description of what you want here.

How would you like the command that puts gitlab-ci-local in "debugging-mode" to look like?

@aleixpol
Copy link
Author

I can imagine running gitlab-ci-local $job --shell bash or even just gitlab-ci-local $job --devel and after it executes the CI suite you're given a shell with the environment where the system just ran. It would be a good opportunity for running the CI, modifying the code and running again or just generally learning about the execution.

@firecow firecow mentioned this issue Aug 21, 2024
Closed
@KoiFresh KoiFresh linked a pull request Dec 23, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
nice Down prioritized
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: get interactive shell into jobs running in a container KoiFresh/gitlab-ci-local
2 participants
@firecow @aleixpol