You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
153962: roachtest: extend github issue poster to include ip node mapping r=srosenberg,DarrylWong a=williamchoe3
Resolves#138356
#### Motivation
Quality of life improvement, previously to find this information, you would need to find the name of the cluster in`test.log`, then use that cluster name to find it's cluster creation log in `{artifacts_dir}/_runner-logs/cluster-create`.
#### Approach
Get's node ip info from roachprod's `cloud.Cluster`
~~Similar to #151850
~~In the test cleanup phase in `inspectArtifacts` added a new function `gatherNodeIpMapping` which is best effort to gather the cluster information in the log.~~
* ~~First we need to find the right log file given that there could be retries for cluster creation which creates additional log files. Given the naming convention, I opted to the just sort the log files that contained the cluster name. I realized a bit later though that because lexicographical sorting on numerical strings, this approach only works if retry attempts is <10. I was trying to avoid unnecessary string parsing if not needed. Also I would assume cluster retry attempts >=10 would be rare / too high of a retry limit to be ever set.~~
After finding the correct file, use regex to find the string in the log. Then store it in `test_impl`, then pass to `issues.Post` and I added a new case for parsing out the IP table
* The regex is flexible to number of columns so we can change the table fields without having to modify the regex
Adds Cluster Node IP information to github issue e.g.
```
| Node | Private IP | Public IP | Machine Type |
| --- | --- | --- | --- |
| willchoe-1758834520-01-n1cpu4-0001 | 10.142.0.2 | 34.139.44.53 | n2-standard-4 |
```
* Opted for keep the VM name as is vs. replacing with something like `n1`. My thinking was that if people wanted to reference the vm in logs, it would be nice to keep the names consistent, but if folks want this as n1 / the vm name isn't helpful then happy to change to `n1`, etc.
Also added a new `node-ips.log` that will also contain this table
#### Notes
Saw "cluster-create" being used as a magic string so created a const for it `clusterCreateDir = "cluster-create"`
#### Verification
Added datadriven test
Manual Verification
Verified the renderer in `issues` was formatting the new code block correctly in debug mode, holding off on generating more debug github issues, but can if folks want to see
156489: sql, sqlstats: Refactor Statement Recording r=kyle-a-wong a=kyle-a-wong
A new RecordedStatementStatsBuilder was added to the sql package to make building a RecordedStmtStats struct easier.
New interfaces were also added to sqlstats to make make building RecordedStmtStats easier.
These new interfaces and builders should help to decouple Recording statement stats from the conn executor, allowing them to be recorded in other places as well
Epic: None
Release note: None
Co-authored-by: William Choe <[email protected]>
Co-authored-by: Kyle Wong <[email protected]>
0 commit comments