-
-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Queues - Ensure that queue timings work, even with bad tzdata #25363
Conversation
(Standard links)
|
Test fail seems to relate
|
Yeah, I haven't quite figured out why -- but I bisected the changes, and it has something to do with the update to |
41a0219
to
d4ef7d8
Compare
Fixed by telling
|
My general take is that the tests are passing & they are the most strict consumer of this code - but I have not actually merged at this stage in case @seamuslee001 wants to weigh in |
I'm gonna merge this now - cos all these failing tests are making stuff hard - I'm sure @seamuslee001 can add post-merge comments if need be |
Overview
The queue tests have been reporting different results on different hosts -- e.g. they pass on
test-{1,2,3}
and on my laptop, but they fail on the temporary worker nodes. The difference is thattzdata
does not appear to be loaded on the temp node's copy ofmysqld
.This updates the queuing queries so that the correctness of
tzdata
does not affect the outcome.Before
We can see that
tests/phpunit/api/v4/Entity/QueueTest.php
has several failures in this environment.Note:
After
After: It doesn't matter if mysqld has tzdata. The test passes.
Comments
I'm not sure if this reflects a substantive bug for typical runtimes. It might... or it might be that the test-suite requires more unusual situations.