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

Test run summary - host info #34

Open
nirs opened this issue Mar 16, 2025 · 0 comments · May be fixed by #48
Open

Test run summary - host info #34

nirs opened this issue Mar 16, 2025 · 0 comments · May be fixed by #48
Assignees
@nirs
Labels
scheduled Scheduled for next release
Milestone
v0.1.0

Comments

@nirs
Copy link
Member

nirs commented Mar 16, 2025 •
edited
Loading

When we debug issues with ramenctl command, it would be useful to have some info on the host running the command.

This should be part of the report yaml file. Every command should write a yaml file in standard format with all info about the host and ramenctl to make debugging issues easier.

host:
  os: darwin
  arch: arm64
  version: "macOS 15.3.2"
ramenctl:
  version: v0.1.0
  commit: eb92ed81e2715d286bfd8ce173c76d4ecda9e2b4

Issues:

  • Getting OS information probably requires os specific code. For now we will report it only if available via go standard library.
@nirs nirs mentioned this issue Mar 16, 2025
Merged
@nirs nirs added this to the v0.2.0 milestone Mar 16, 2025
@nirs nirs added the scheduled Scheduled for next release label Mar 17, 2025
@nirs nirs changed the title Gather host info in command report Test run summary - host info Mar 17, 2025
@nirs nirs modified the milestones: v0.2.0, v0.1.0 Mar 18, 2025
@nirs nirs self-assigned this Mar 19, 2025
@nirs nirs linked a pull request Mar 19, 2025 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

@nirs nirs

Labels
scheduled Scheduled for next release
Projects
None yet
Milestone
v0.1.0
Development

Successfully merging a pull request may close this issue.

Add test report nirs/ramenctl
1 participant
@nirs