Backport to 17.0: Fix JobArtifactState query timeout
What does this MR do and why?
Describe in detail what merge request is being backported and why
Backports Resolve "JobArtifactState.checksummed_count query timing out"
to 17.1.
Original merge request: !158901 (merged)
Original issue: #471727 (closed)
Backport request issue: https://gitlab.com/gitlab-org/release/tasks/-/issues/12953
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch. -
The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes). -
This MR has a severity label assigned (if applicable). -
Set the milestone of the merge request to match the target backport branch version. -
This MR has been approved by a maintainer (only one approval is required). -
Ensure the e2e:test-on-omnibus-ee
job has either succeeded or been approved by a Software Engineer in Test.
Note to the merge request author and maintainer
If you have questions about the patch release process, please:
- Refer to the patch release runbook for engineers and maintainers for guidance.
- Ask questions on the
#releases
Slack channel (internal only).
Merge request reports
Activity
changed milestone to %17.0
assigned to @mkozono
3 Warnings There were no new or modified feature flag YAML files detected in this MR. If the changes here are already controlled under an existing feature flag, please add
the feature flagexists. Otherwise, if you think the changes here don't need
to be under a feature flag, please add the label feature flagskipped, and
add a short comment about why we skipped the feature flag.For guidance on when to use a feature flag, please see the documentation.
Backporting to older releases requires an exception request process The e2e:package-and-test-ee
job needs to succeed or have approval from a Software Engineer in Test.
Read the "QA e2e:package-and-test-ee" section for more details.1 Message CHANGELOG missing: If this merge request needs a changelog entry, add the
Changelog
trailer to the commit message you want to add to the changelog.If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
Reviewer roulette
Category Reviewer Maintainer backend @lesley-r
(UTC-5, 5 hours ahead of author)
@pskorupa
(UTC+2, 12 hours ahead of author)
Please check reviewer's status!
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.
QA
e2e:package-and-test-ee
@mkozono, the
package-and-test
job must complete before merging this merge request.*If there are failures on the
package-and-test
pipeline, ping your team's associated Software Engineer in Test (SET) to confirm the failures are unrelated to the merge request. If there's no SET assigned, ask for assistance on the#test-platform
Slack channel.If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangermentioned in issue #471727 (closed)
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-package-and-test:
test report for df284b31expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Verify | 154 | 0 | 36 | 0 | 190 | ✅ | | Create | 320 | 0 | 34 | 0 | 354 | ✅ | | Plan | 48 | 0 | 0 | 0 | 48 | ✅ | | Release | 2 | 0 | 0 | 0 | 2 | ✅ | | Govern | 28 | 0 | 0 | 0 | 28 | ✅ | | Package | 6 | 0 | 8 | 0 | 14 | ✅ | | Monitor | 8 | 0 | 0 | 0 | 8 | ✅ | | Data Stores | 22 | 0 | 0 | 0 | 22 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 588 | 0 | 78 | 0 | 666 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
changed milestone to %17.4
added missed:17.0 label
@dbalexandre Would you please review?
requested review from @dbalexandre
added pipeline:mr-approved label
added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-1 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.
- Resolved by Michael Kozono
@dbalexandre
, thanks for approving this merge request.This is the first time the merge request has been approved. Please ensure the
e2e:test-on-omnibus-ee
job has succeeded. If there is a failure, a Software Engineer in Test (SET) needs to confirm the failures are unrelated to the merge request. If there's no SET assigned to this team, ask for assistance on the#test-platform
Slack channel.
removed pipeline:run-e2e-omnibus-once label
Failure in
start-as-if-foss
pipeline'srspec integration pg14 single-db 1/16
https://gitlab.com/gitlab-org/gitlab-foss/-/jobs/7766598233 looks irrelevant:Spawning Gitaly 02:19 Trying to connect to gitaly: ...................... OK /builds/gitlab-org/gitlab-foss/spec/support/helpers/gitaly_setup.rb:324:in `rescue in spawn_gitaly': gitaly spawn failed (RuntimeError) Check log/gitaly-test.log & log/praefect-test.log for errors. from /builds/gitlab-org/gitlab-foss/spec/support/helpers/gitaly_setup.rb:300:in `spawn_gitaly' from scripts/gitaly-test-spawn:20:in `run' from scripts/gitaly-test-spawn:24:in `<main>' /builds/gitlab-org/gitlab-foss/spec/support/helpers/gitaly_setup.rb:199:in `try_connect!': could not connect to gitaly2 (RuntimeError) from /builds/gitlab-org/gitlab-foss/spec/support/helpers/gitaly_setup.rb:135:in `start' from /builds/gitlab-org/gitlab-foss/spec/support/helpers/gitaly_setup.rb:108:in `start_gitaly2' from /builds/gitlab-org/gitlab-foss/spec/support/helpers/gitaly_setup.rb:307:in `spawn_gitaly' from scripts/gitaly-test-spawn:20:in `run' from scripts/gitaly-test-spawn:24:in `<main>' Trying to connect to gitaly2: ........................................................................................................................................................................................................ FAILED to connect to gitaly2
Update: The latest retry did not see this job failure.
Edited by Michael Kozonostarted a merge train
removed this merge request from the merge train because the pipeline did not succeed. Learn more.
started a merge train
mentioned in commit 697b5172