Add back sharding_key_issue_url
What does this MR do and why?
This MR adds back the sharding_key_issue_url
for the p_ci_finished_build_ch_sync_events
table, since there are still steps to complete in #459997 (closed).
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Merge request reports
Activity
changed milestone to %17.4
added Category:Fleet Visibility devopsverify grouprunner sectionci labels
assigned to @pedropombeiro
added pipelinetier-1 label
removed pipelinetier-1 label
added maintenancerefactor label
added typemaintenance label
- A deleted user
added database databasereview pending labels
1 Warning The master pipeline status page reported failures in - rspec-ee unit pg14 single-db-ci-connection 26/39
- rspec-ee unit pg14 single-db 32/39
- rspec integration pg14 single-db 1/20
- rspec unit pg14 single-db-ci-connection 35/44
- rspec unit pg14 single-db-ci-connection 11/44
- rspec unit pg14 single-db-ci-connection 1/44
- rspec unit pg14 single-db 14/44
- rspec unit pg14 single-db 6/44
If these jobs fail in your merge request with the same errors, then they are not caused by your changes.
Please check for any on-going incidents in the incident issue tracker or in the#master-broken
Slack channel.Reviewer roulette
Category Reviewer Maintainer database @ifarkas
(UTC+2, same timezone as author)
@cablett
(UTC+12, 10 hours ahead of author)
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangerrequested review from @shubhamkrai
- Resolved by Omar Qunsul
requested review from @dstull
added pipeline:mr-approved label
added pipelinetier-2 label
Thank you @pedropombeiro
mentioned in issue #459997 (closed)
requested review from @OmarQunsulGitlab and removed review request for @dstull and @shubhamkrai
added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-2 label
Before you set this MR to auto-merge
This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.
Before you set this MR to auto-merge, please check the following:
- You are the last maintainer of this merge request
- The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
- This pipeline is recent enough (created in the last 8 hours)
If all the criteria above apply, please set auto-merge for this merge request.
See pipeline tiers and merging a merge request for more details.
added databaseapproved label and removed databasereview pending label
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for 38311865expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Plan | 74 | 0 | 1 | 0 | 75 | ✅ | | Package | 20 | 0 | 12 | 0 | 32 | ✅ | | Create | 128 | 0 | 16 | 0 | 144 | ✅ | | Data Stores | 31 | 0 | 1 | 0 | 32 | ✅ | | Govern | 72 | 0 | 0 | 0 | 72 | ✅ | | Release | 5 | 0 | 0 | 0 | 5 | ✅ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | Verify | 44 | 0 | 2 | 0 | 46 | ✅ | | Monitor | 8 | 0 | 0 | 0 | 8 | ✅ | | Secure | 4 | 0 | 0 | 0 | 4 | ✅ | | Manage | 1 | 0 | 1 | 0 | 2 | ✅ | | Fulfillment | 2 | 0 | 0 | 0 | 2 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 391 | 0 | 33 | 0 | 424 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
removed pipeline:run-e2e-omnibus-once label
started a merge train
removed this merge request from the merge train because the pipeline did not succeed. Learn more.
started a merge train
Hello @pedropombeiro
The database team is looking for ways to improve the database review process and we would love your help!
If you'd be open to someone on the database team reaching out to you for a chat, or if you'd like to leave some feedback asynchronously, just post a reply to this comment mentioning:
@gitlab-org/database-team
And someone will be by shortly!
Thanks for your help!
This message was generated automatically. You're welcome to improve it.
mentioned in commit ba8b97db
mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#8368 (closed)
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label