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.

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

roachtest: surface cloud cluster spec info in artifacts #124243

Merged
merged 1 commit into from
May 20, 2024

Conversation

vidit-bhat
Copy link
Contributor

@vidit-bhat vidit-bhat commented May 15, 2024

Previously, getting the spec of the VMs on which a roachtest ran was tricky to derive.
This was inadequate because it's often necessary to understand the particulars of a roachtest run's environment.
To address this, this patch creates a json file per VM describing its spec. These files are stored under artifacts/vm_spec.

Epic: none
Fixes: #112707
Release note: None

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@vidit-bhat vidit-bhat force-pushed the roachtest-surface-vm-spec branch 4 times, most recently from 4dfb0fe to 5d7bc8c Compare May 16, 2024 11:17
@vidit-bhat vidit-bhat marked this pull request as ready for review May 16, 2024 11:20
@vidit-bhat vidit-bhat requested a review from a team as a code owner May 16, 2024 11:20
@vidit-bhat vidit-bhat requested review from herkolategan, nameisbhaskar, srosenberg, DarrylWong and renatolabs and removed request for a team May 16, 2024 11:20
Copy link
Contributor

@DarrylWong DarrylWong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it seems like we only surface this info if the test fails? I think that's fine in the context of using this to debug test failures, but just making sure that's the intention here.

if err != nil {
return err
}
providerToVMs := bucketVMsByProvider(cachedCluster)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could use vm.FanOut instead if you wanted to. Might be slightly simpler. It collates vms by a provider and calls the function passed to it, basically what you're doing here.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will take this up in a follow up PR. Do you think we should use vm.FanOut for GetPreemptedVMs and GetHostErrorVMs as well?

@vidit-bhat
Copy link
Contributor Author

So it seems like we only surface this info if the test fails? I think that's fine in the context of using this to debug test failures, but just making sure that's the intention here.

Yes that's the intention

@vidit-bhat vidit-bhat force-pushed the roachtest-surface-vm-spec branch 2 times, most recently from 33a1564 to 5021905 Compare May 17, 2024 16:12
Copy link
Contributor

@DarrylWong DarrylWong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another small nit but otherwise LGTM!

Previously, getting the spec of the VMs on which a roachtest
ran was tricky to derive.
This was inadequate because it's often necessary to understand
the particulars of a roachtest run's environment.
To address this, this patch creates a json file per VM describing
its spec in. These files are stored in the Artifacts directory.

Epic: none
Fixes: cockroachdb#112707
Release note: None
@vidit-bhat vidit-bhat force-pushed the roachtest-surface-vm-spec branch from 5021905 to 0e3ae2c Compare May 20, 2024 05:58
@vidit-bhat
Copy link
Contributor Author

bors r+

@craig craig bot merged commit 99d7687 into cockroachdb:master May 20, 2024
22 checks passed
vidit-bhat added a commit to vidit-bhat/cockroach that referenced this pull request May 22, 2024
This is a follow up PR to cockroachdb#124243.
It implements the surfacing of cluster specs for aws and refactors
logic in `cluster.go` to make it cloud agnostic.

Epic: none
Release note: None
vidit-bhat added a commit to vidit-bhat/cockroach that referenced this pull request May 23, 2024
This is a follow up PR to cockroachdb#124243.
It implements the surfacing of cluster specs for aws and refactors
logic in `cluster.go` to make it cloud agnostic.

Epic: none
Release note: None
craig bot pushed a commit that referenced this pull request May 23, 2024
124443: roachtest: surface cloud cluster spec info in artifacts for aws r=vidit-bhat a=vidit-bhat

This is a follow up PR to #124243. It implements the surfacing of cluster specs for `aws` and refactors logic in `cluster.go` to make it cloud agnostic.

Epic: none
Release note: None

Co-authored-by: Vidit Bhat <[email protected]>
@vidit-bhat
Copy link
Contributor Author

blathers backport 24.1 23.2

Copy link

blathers-crl bot commented May 24, 2024

Encountered an error creating backports. Some common things that can go wrong:

  1. The backport branch might have already existed.
  2. There was a merge conflict.
  3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.


error creating merge commit from 0e3ae2c to blathers/backport-release-23.2-124243: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 23.2 failed. See errors above.


🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

blathers-crl bot pushed a commit that referenced this pull request May 25, 2024
This is a follow up PR to #124243.
It implements the surfacing of cluster specs for aws and refactors
logic in `cluster.go` to make it cloud agnostic.

Epic: none
Release note: None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

roachtest: surface cloud cluster spec info in artifacts
5 participants