User Details
- User Since
- Jan 12 2022, 10:04 AM (139 w, 4 d)
Thu, Sep 5
Tue, Sep 3
Wed, Aug 28
Wed, Aug 21
Tue, Aug 20
This disables glib aborting after an error message.
Related, we have this in logging.c:
My first thought here is to start by converting pcmk__remote_ready to be an async function that checks the remote to see if it's ready once and sends a result up to the mainloop. However, one caller of this function is lrmd_poll, which we do not use anywhere but I assume is public API. Do we need to continue keeping it (and lrmd_dispatch) around? If so, we might need sync and async versions of this function.
Aug 9 2024
Aug 8 2024
Jul 31 2024
Jul 29 2024
Jul 10 2024
I think those are the only three tests in cts-scheduler that also have a third argument to SchedulerTest. This is probably something I broke in one of the refactoring rounds.
It's odd that they would only fail when run individually. One clue as to what's going wrong might be that those are the only three tests with the string "Setting effective cluster time" in their summary files, and that string comes from set_effective_date.