-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: django failed #76011
Comments
There were some new cluster settings added that might have made this test a bit unstable (#75989). The settings were added to improve testing performance. We'll see how flaky this is over the next few runs. There's other work that should land soon that will make some of these settings not needed. |
roachtest.django failed with artifacts on master @ 8548987813ff9e1b8a9878023d3abfc6911c16db:
|
roachtest.django failed with artifacts on master @ 8548987813ff9e1b8a9878023d3abfc6911c16db:
|
roachtest.django failed with artifacts on master @ 8548987813ff9e1b8a9878023d3abfc6911c16db:
|
roachtest.django failed with artifacts on master @ a7b1c17c240c935056f87f29dfc1ee75611c371e:
|
roachtest.django failed with artifacts on master @ 432a383c1a7509762ce66a2b9ae7869d82da5f31:
|
roachtest.django failed with artifacts on master @ d10188f400deafa2569b052cd3e9fd9713783ed9:
|
roachtest.django failed with artifacts on master @ 84a0e500920e6d0b935d2007de256e42822e94c7:
|
76394: sql: use IndexFetchSpec in TableReader r=RaduBerinde a=RaduBerinde #### row: replace fetcher args with IndexFetchSpec This commit replaces the row fetcher table args with IndexFetchSpec. Release note: None #### sql: use IndexFetchSpec in TableReader This commit removes the table descriptor from TableReader and replaces it with an IndexFetchSpec. Eventually, we will use the same `IndexFetchSpec` to form the columnar batch directly in KV. Release note: None 76415: dev: address a few paper cuts r=irfansharif a=irfansharif See individual commits, works through a few of the known paper cuts with dev/bazel (#75453). 76420: sql: initialize tenant span config with rangefeeds enabled r=irfansharif a=ajwerner Not doing this causes problems when we construct new tenants as they won't be able to establish a rangefeed until their first full reconciliation completes and then propagates. Even this is not great. If the preceding range did not have rangefeeds enabled, it would take a closed timestamp interval for this enablement to propagate. Perhaps this is evidence that we should always carve out a span at the end of the keyspace and set it to have rangefeeds enabled. I'll leave that fix and testing of this to somebody else. Hope this is helpful enough on its own. cc `@irfansharif` and `@arulajmani.` I believe this problem has been blocking `@RaduBerinde.` Fixes #76331 Release note: None 76437: clisqlshell: handle interactive query cancellation r=rafiss a=knz Fixes #76433. As of this PR, there's a bug in lib/pq which forces the session to terminate when any query gets cancelled. We find this unacceptable and we plan to fix it later. Release note (cli change): The interactive SQL shell (`cockroach sql`, `cockroach demo`) now supports interrupting a currently running query with Ctrl+C, without losing access to the shell. 76442: roachtest: try to stabilize ORM nightlies r=RichardJCai a=rafiss fixes #76428 fixes #76426 fixes #68363 touches #76231 touches #76016 touches #76011 Ruby-pg and psycopg2 tests started passing because we now support pgwire cancel. Other tests (Django, Hibernate, and PGJDBC) seem flaky after the testing settings change, so try to use slightly more conservative values. Release note: None 76450: ci: add extra logging of `$TC_SERVER_URL` in pebble metamorphic nightly r=nicktrav a=rickystewart Release note: None Co-authored-by: Radu Berinde <[email protected]> Co-authored-by: irfan sharif <[email protected]> Co-authored-by: Andrew Werner <[email protected]> Co-authored-by: Raphael 'kena' Poss <[email protected]> Co-authored-by: Rafi Shamim <[email protected]> Co-authored-by: Ricky Stewart <[email protected]>
roachtest.django failed with artifacts on master @ 8548987813ff9e1b8a9878023d3abfc6911c16db:
Help
See: roachtest README
See: How To Investigate (internal)
This test on roachdash | Improve this report!
The text was updated successfully, but these errors were encountered: