-
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: tpccbench/nodes=3/cpu=4 failed #54822
Comments
|
Fallout from #54772? @RaduBerinde I stop using fixtures entirely for tpccbench in #53983. It seems like that would save a lot of work here. Should we just push that forward? |
That change wasn't on any of the release branches yet.. Do we run workload from master against older versions? |
@RaduBerinde yeah, I think |
Yes, sigh. #51897 pls |
I think I see what's going on. tpccbench passes the |
Hm, though I don't know why that flag wouldn't show up in this log:
|
I think I figured it out. The fixture exists (or we would be getting a "cannot find fixture" error). The error comes from loading a backup which doesn't have the FK indexes, required by 20.1. I will try to figure out where the error comes from and if we can make it less opaque. The problem is that we are not passing the |
I wasn't quite right. The error is indeed coming from google cloud storage. The old version is looking for a |
(roachtest).tpccbench/nodes=3/cpu=4 failed on release-20.1@5a4e41010f8faa095c88e2e5b142e0b6880c9f44:
More
Artifacts: /tpccbench/nodes=3/cpu=4
See this test on roachdash |
(roachtest).tpccbench/nodes=3/cpu=4 failed on release-20.1@d89343cdb6dcd86584584b098889795620dfd534:
More
Artifacts: /tpccbench/nodes=3/cpu=4
See this test on roachdash |
54743: kvcoord: properly redact 'have been waiting' message in DistSender r=knz a=tbg Release note: None 55050: roachtest: use crdb's workload for fixtures import tpcc r=nvanbenschoten a=nvanbenschoten Fixes #55042. Fixes #55041. Fixes #55039. Fixes #55038. Fixes #55037. Fixes #55036. Fixes #55035. Fixes #55033. Fixes #55029. Fixes #55024. Fixes #55022. Fixes #55020. Fixes #55019. Fixes #55018. Fixes #55017. Fixes #55016. Fixes #55013. Fixes #55010. Fixes #55009. Fixes #55008. Fixes #55003. Fixes #55002. Fixes #54998. Fixes #54995. Fixes #54822. Fixes #52693. Fixes #54802. We were already doing this in some places, but needed it in others. Co-authored-by: Tobias Grieger <tobias.b.grieger@gmail.com> Co-authored-by: Nathan VanBenschoten <nvanbenschoten@gmail.com>
Fixes #55042. Fixes #55041. Fixes #55039. Fixes #55038. Fixes #55037. Fixes #55036. Fixes #55035. Fixes #55033. Fixes #55029. Fixes #55024. Fixes #55022. Fixes #55020. Fixes #55019. Fixes #55018. Fixes #55017. Fixes #55016. Fixes #55013. Fixes #55010. Fixes #55009. Fixes #55008. Fixes #55003. Fixes #55002. Fixes #54998. Fixes #54995. Fixes #54822. Fixes #52693. Fixes #54802. We were already doing this in some places, but needed it in others.
(roachtest).tpccbench/nodes=3/cpu=4 failed on release-20.1@a84063ed9e7e3c43c710534629399bb957f17cca:
More
Artifacts: /tpccbench/nodes=3/cpu=4
Related:
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: