roachtest: multitenant-upgrade failed #91589
Assignees
Labels
branch-master
Failures and bugs on the master branch.
C-test-failure
Broken test (automatically or manually discovered).
O-roachtest
O-robot
Originated from a bot.
Milestone
Comments
cockroach-teamcity
added
branch-master
|
@ajstorm wanna have a look? |
|
Yeah, this is definitely me. Taking a look now.
…On Wed, Nov 9, 2022 at 5:50 AM knz ***@***.***> wrote:
@ajstorm <https://github.com/ajstorm> wanna have a look?
—
Reply to this email directly, view it on GitHub
<#91589 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEMXVOXG2BL427WQUN5NHG3WHN6WVANCNFSM6AAAAAAR3I4SMY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
ajstorm
removed
the
release-blocker
|
roachtest.multitenant-upgrade failed with artifacts on master @ d6ae9653b67071cca09ed296711cecc821fc284e: Parameters: |
craig bot
pushed a commit
that referenced
this issue
Nov 10, 2022
91081: ui: migrate statement diagnostics requests to use sql-over-http endpoint r=THardy98 a=THardy98 Part of: #89429 Addresses: #90273, #90274, #90275 Blocked from resolving by #80789 DB-Console Demo: https://www.loom.com/share/d74c02eb3dfb41fc913577d0e8992441 CC-Console Demo: https://www.loom.com/share/2adba8a53b8c48ac9f031e4481f284cf This change migrates the existing statement diagnostics requests to use the sql-over-http endpoint on our apiV2, making these requests tenant-scoped once the sql-over-http endpoint is scoped to tenants (this should be the case when #91323 is completed). 91534: lint: remove Golint r=yuzefovich a=yuzefovich This commit removes `TestGolint` linter as well as all mentions of `golint` I could find. The rationale is that - the linter is no longer maintained - is partially duplicated with the `staticcheck` - due to a recent change in `gcexportdata.Find`, if we bump some dependencies, it takes on the order of an hour when run via bazel, and we'd need to fork `golint` to go around that. Epic: None Release note: None 91626: kvstreamer: improve the behavior with very low budget r=yuzefovich a=yuzefovich This commit makes it so that the streamer tries a bit harder to not hit its low budget limit in `Enqueue`. Previously, due to some of the internal state being reused across different `Enqueue` batches (in particular, the truncation helper as well as some things in the results buffer), the streamer's budget might be insufficient to account for the newly-enqueued requests, and we would error out. This commit makes it so that - if the budget limit is reached - we first discard the overhead (freeing up some budget) and then try to consume the requests' footprint again. This shouldn't be a big deal with reasonably large workmem limits, but we have seen some problems when it is on the order of 100KiB or less. Fixes: #91587. Release note: None 91662: multi-tenant: Bump uninitialized storage cluster version r=knz a=ajstorm Previously, in cases where the version value in system.tenant_settings was uninitialized, we assumed that that the version was 22.1. With the change of the build tag to 23.1, we need to adjust the previous version to 22.1.76. This will need one more bump when we finally mint the 22.2 version number in master. Resolves: #91589 Release note: None Co-authored-by: Thomas Hardy <[email protected]> Co-authored-by: Yahor Yuzefovich <[email protected]> Co-authored-by: Adam Storm <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
roachtest.multitenant-upgrade failed with artifacts on master @ ee4fdb7fff683a7916ee585ac0c1e22d5d9a4412:
Parameters:
ROACHTEST_cloud=gce,ROACHTEST_cpu=4,ROACHTEST_encrypted=false,ROACHTEST_fs=ext4,ROACHTEST_localSSD=true,ROACHTEST_ssd=0Help
See: roachtest README
See: How To Investigate (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-21337
The text was updated successfully, but these errors were encountered: