-
Notifications
You must be signed in to change notification settings - Fork 1.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
chore: bump k6 operator to v0.0.14 #7730
base: master
Are you sure you want to change the base?
Conversation
/ok-to-perf |
Dapr perf testCommit ref: 70f49e4 ✅ Build succeeded
✅ Infrastructure deployed
❌ Perf tests failedPlease check the logs for details on the error. |
That was a valiant effort. We are blocked on this: kubernetes-sigs/kubebuilder#3792 (comment) |
Signed-off-by: mikeee <hey@mike.ee>
/ok-to-perf |
Dapr perf testCommit ref: 2590452 ✅ Build succeeded
✅ Infrastructure deployed
|
@yaron2 I've got the perf tests running using a k6-operator fork, but I'm concerned about the high failure rate of the tests anyway. Is this flakiness or kubebuilder-blocking? |
/ok-to-test |
Dapr E2E testCommit ref: 2590452 ✅ Build succeeded for linux/amd64
✅ Infrastructure deployed
✅ Build succeeded for windows/amd64
❌ Tests failed on windows/amd64Please check the logs for details on the error. ✅ Tests succeeded on linux/amd64
|
/ok-to-perf |
Dapr perf testCommit ref: 2590452 ✅ Build succeeded
✅ Infrastructure deployed
|
/ok-to-perf |
Dapr perf testCommit ref: 2590452 ✅ Build succeeded
✅ Infrastructure deployed
|
/ok-to-perf |
Dapr perf testCommit ref: 2590452 ✅ Build succeeded
✅ Infrastructure deployed
|
/ok-to-perf |
Dapr perf testCommit ref: 2590452 ✅ Infrastructure deployed
✅ Build succeeded
|
Description
quick test to see if this is the source of perf tests failing
Issue reference
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: