roachtest: weekly/tpcc/headroom failed [infra problems] #47652
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
|
(roachtest).weekly/tpcc/headroom failed on master@0e16cc15f139b816b8e46fe6571691a8ec0e6937: |
|
(roachtest).weekly/tpcc/headroom failed on master@61f18db7dd9a054d9a4648f67546202f760b5000: |
|
(roachtest).weekly/tpcc/headroom failed on master@f6ce99f3e8c70059afdcb7683432cde5007c5102: |
This looks like clock skew. Is there anything actionable? |
|
(roachtest).weekly/tpcc/headroom failed on master@2dd15cd26f95801c678b1034e98a15560dc10baa: |
|
(roachtest).weekly/tpcc/headroom failed on master@d3791a81c0716478de08d44459d3fcf5b4f3ea1e: |
|
(roachtest).weekly/tpcc/headroom failed on master@112ff533bf079fb057aadf5a998d9e1f09e6aa1f: |
|
(roachtest).weekly/tpcc/headroom failed on master@542c83e7db1694208e09c7fea7d350db4993b897: |
|
(roachtest).weekly/tpcc/headroom failed on master@af0031e3004327b8d09e23e99eb9659abf7d82de: |
|
(roachtest).weekly/tpcc/headroom failed on master@bfa6307c292ef4dfed4a53cb99f506e6dab26533: |
|
This latest error is different from the earlier failure. It indicates a |
|
The last failure seems to be |
|
(roachtest).weekly/tpcc/headroom failed on master@8bdf6ba0f908f562822348300597b9f435f478d1: |
|
(roachtest).weekly/tpcc/headroom failed on master@d310eb8eb6da5df4ac4407a2c90d898acdfdddf3: |
|
(roachtest).weekly/tpcc/headroom failed on master@1049eaa26d983a0449049264d6c2ee2cc27454e2: |
|
(roachtest).weekly/tpcc/headroom failed on master@bbbedabbf6ea0b1ff6fc799a0c04a75295a9f4c2: |
|
(roachtest).weekly/tpcc/headroom failed on master@123ca0782f423bc3d225a5ca798ece60c3185935: |
again this looks like infra flake. Do we want to mark the test as failed in that case? @jlinder is there a way to make the test report as non-failed when this symptom is encountered? |
knz
removed
the
release-blocker
|
It seems to fail like that every week, so there's definitely something to investigate here. Can this really be true? |
|
(roachtest).weekly/tpcc/headroom failed on master@9fae2abb48a00c26ac0344f35cd100df7faa2aec: |
|
(roachtest).weekly/tpcc/headroom failed on master@339275585b7d30b9ee2d49b0c696b9ddb8d51ad4: |
|
(roachtest).weekly/tpcc/headroom failed on master@a786c51627fe66e47b4a4445c67b2a9077ae2a93: |
This looks concerning. |
|
I believe the |
This was referenced Jan 15, 2021
|
No, thanks Yahor!
…On Fri, Jan 15, 2021, 19:02 Yahor Yuzefovich ***@***.***> wrote:
I believe the nonzero results failure is the same as #58935
<#58935> which I have a PR
open to fix. @tbg <https://github.com/tbg> @andreimatei
<https://github.com/andreimatei> do you guys want this issue to be closed
when that PR merges?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#47652 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGXPZBCIDEDFFR4N7N35HDS2B7L5ANCNFSM4MLHMCPQ>
.
|
craig bot
pushed a commit
that referenced
this issue
Jan 15, 2021
58713: ui: add eslint with shared config r=dhartunian a=dhartunian Our UI codebase does not have standardized formatting yet. In order to get to a point where we can enforce these standards, we're adding the ability to run `eslint` for UI code in `pkg/ui`. A base set of ignored rules is added in `package.json` in order to get a clean run. It is our intention to eventually remove these ignored rules once we clean up the codebase further. Currently they result in over 1500 warnings. We are also removing the use of the `tslint` tool as `eslint` is preferred for TypeScript linting as well. `eslint` will now run as part of the Makefile `ui-lint` task. Further PRs will contain formatting fixes to get eslint to pass. Depends on: cockroachdb/yarn-vendored#48 Release note: none 58877: filetable: read chunks as needed r=dt a=dt This changes filetable to read only the block needed from the table instead of reading the whole file at once. Release note: none. 59057: colexec: fix coalescing logic in the spilling queue r=yuzefovich a=yuzefovich In a recently merged change to the spilling queue we introduced a bug in the coalescing logic - we incorrectly computed the index of the "tail" batch in case when it is the last one in the in-memory buffer. This could lead to multiple problems (modification of the filled-up batch, of the already dequeued batch, etc). This is now fixed. Additionally, this commit switches to using `Copy` instead of `Append` in that coalescing logic (since we know that there is enough capacity for all of the tuples we're appending) and sets the item to `nil` when it was dequeued. Addresses: #47652. Fixes: #58913. Fixes: #58915. Fixes: #58934. Fixes: #58935. Fixes: #58936. Fixes: #58956. Release note: None (no stable release with this bug) Co-authored-by: David Hartunian <davidh@cockroachlabs.com> Co-authored-by: David Taylor <tinystatemachine@gmail.com> Co-authored-by: Yahor Yuzefovich <yahor@cockroachlabs.com>
|
(roachtest).weekly/tpcc/headroom failed on master@baf34b241c9ee27530f0a3a988149bfd7cca3f6d: |
|
(roachtest).weekly/tpcc/headroom failed on master@86c619f768a4d6f4cc80efb5c9479e5fc0fd72c1: |
|
(roachtest).weekly/tpcc/headroom failed on master@c584f62067a45aa540c26fc9081a83e460bfe37a: |
|
(roachtest).weekly/tpcc/headroom failed on master@e9e372122a2e3db7090b5705da07128f828e2441: |
|
(roachtest).weekly/tpcc/headroom failed on master@83e70ce84b740e27e721c3b73c38a4b8b515094a: |
|
(roachtest).weekly/tpcc/headroom failed on master@6601d827b814d4e85a1081b03bf2562d8ac2a4ab: |
|
(roachtest).weekly/tpcc/headroom failed on master@b703e663da8ededaee2e28fc39a24e3880ae54cf: |
|
(roachtest).weekly/tpcc/headroom failed on master@4b98115dfda02a9498f566958bd915c45ec7e449: |
|
(roachtest).weekly/tpcc/headroom failed on master@ee9f47b9ec9476a693464e2dcd09a01bf9d39ad2: |
|
(roachtest).weekly/tpcc/headroom failed on master@f84a9da9e62bad67c6a72d6c0717cd87e2372357: |
|
(roachtest).weekly/tpcc/headroom failed on master@8b137b4f068a0d590a3e86ae91fd60eb84f2750a: |
|
Tracked in #62946 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(roachtest).weekly/tpcc/headroom failed on master@a63a670b1a591be2ed38af7f98c1f85e32546596:
More
Artifacts: /weekly/tpcc/headroom
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: