- Issue created by @catch
- First commit to issue fork.
- Status changed to Needs work
12 months ago 12:06am 7 March 2024 - 🇨🇭Switzerland berdir Switzerland
Went down quite a rabbit hole of getting our GitlabCI configuration updated to run on next minor/major. And that's all green now, but I did _not_ yet do anything about the QueueFactoryInterface. Which I think shows that we are missing test coverage for that. There really aren't many things in core doing queue stuff, and we're not yet triggering that in the web test. The queue kernel tests apparently bypass the factory/discovery, so that still works.
- Status changed to Active
11 months ago 9:25pm 24 March 2024 - 🇨🇭Switzerland berdir Switzerland
Committed these changes in 📌 Expand CI testing to next minor/major, fix tests on 10.2 Fixed so this can then focus on the Queue stuff.
Interestingly, neither our queue kernel tests nor the web test is actually failing on this on D11. There is barely anything left in core that can be used for real-world queue testing.
- Status changed to Fixed
9 months ago 10:35am 8 June 2024 - 🇨🇭Switzerland berdir Switzerland
Nothing in core verifies this, so it's not possible to have failing tests. Merged.
Automatically closed - issue fixed for 2 weeks with no activity.