Bump migrations CPU limit from 600m to 800m
What does this MR do and why?
Increase review-apps CPU limit from 600m to 800m, so that we see less alerts in our monitoring.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
changed milestone to %15.8
added Engineering Productivity maintenancerefactor + 1 deleted label
assigned to @ddieulivol
added typemaintenance label
marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed
- Resolved by Rémy Coutable
Hey @rymai, Could you please review this MR? Thanks in advance
requested review from @rymai
Reviewer roulette
Changes that require review have been detected!
Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:
Category Reviewer Maintainer maintenanceworkflow / maintenancepipelines for CI, Danger Aman Luthra (
@aluthra2
) (UTC+5.5, 4.5 hours ahead of@ddieulivol
)Ethan Urie (
@eurie
) (UTC-5, 6 hours behind@ddieulivol
)To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
DangerEdited by Ghost UserAllure report
allure-report-publisher
generated test report!e2e-review-qa:
test report for 3e040a9eexpand test summary
+-----------------------------------------------------------------------------------------+ | suites summary | +------------------------------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +------------------------------------+--------+--------+---------+-------+-------+--------+ | Govern | 15 | 0 | 5 | 3 | 20 | ❗ | | Create | 28 | 0 | 1 | 0 | 29 | ✅ | | Verify | 12 | 0 | 1 | 0 | 13 | ✅ | | Manage | 38 | 0 | 4 | 7 | 42 | ❗ | | Plan | 49 | 0 | 1 | 0 | 50 | ✅ | | Feature flag handler sanity checks | 9 | 0 | 0 | 0 | 9 | ✅ | | Version sanity check | 0 | 0 | 1 | 0 | 1 | ➖ | | Package | 0 | 0 | 1 | 0 | 1 | ➖ | | Configure | 0 | 0 | 1 | 0 | 1 | ➖ | +------------------------------------+--------+--------+---------+-------+-------+--------+ | Total | 151 | 0 | 15 | 10 | 166 | ❗ | +------------------------------------+--------+--------+---------+-------+-------+--------+
Edited by Ghost Userchanged milestone to %15.7
@rymai
, thanks for approving this merge request.This is the first time the merge request is approved. To ensure full test coverage, a new pipeline will be started shortly.
For more info, please refer to the following links:
added pipeline:mr-approved label
enabled an automatic merge when the pipeline for 74ffae9e succeeds
mentioned in commit d78f1249
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label