- Status changed to Active
almost 2 years ago 11:24pm 20 February 2023 - Status changed to Needs review
almost 2 years ago 5:36am 22 February 2023 The last submitted patch, 430: 2853234-54.patch, failed testing. View results →
- Status changed to Needs work
almost 2 years ago 5:26am 23 February 2023 - Status changed to Needs review
almost 2 years ago 5:11am 27 February 2023 - Status changed to Active
almost 2 years ago 2:50pm 27 February 2023 - 🇺🇸United States smustgrave
Moving out of the review queue so it doesn't mess with metrics. You can continue to use this ticket just click add test link without moving to review.
- Status changed to Needs review
almost 2 years ago 4:50am 10 March 2023 The last submitted patch, 445: test1.patch, failed testing. View results →
The last submitted patch, 447: 2855653-34.patch, failed testing. View results →
- Status changed to Needs work
almost 2 years ago 5:16am 13 March 2023 - Status changed to Needs review
almost 2 years ago 5:18am 13 March 2023 - Status changed to Active
almost 2 years ago 8:42pm 13 March 2023 - 🇺🇸United States smustgrave
Moving out of the review queue so it doesn't mess with metrics. You can continue to use this ticket just click add test link without moving to review.
- 🇳🇿New Zealand quietone
Just adding a reminder that it is good practice to run the pre-commit checks and other tests locally before uploading a patch. Running the whole suite of tests is not necessary when making a change limited to one subsystem or some minor change.
Instructions are available
Run core development checks →
learning how to run automated tests → on your local machine. - last update
over 1 year ago Build Successful - 🇳🇿New Zealand quietone
Updating the title per the Special issue titles → . Also, this is a task not a support request.