We also need to allow the use of new functions in glib that were introduced later than our minimum supported version, if they are available on the build platform. See https://github.com/ClusterLabs/pacemaker/pull/3929#discussion_r2250963422 for details.

In T982#15872, @clumens wrote:

I bet running this from a source directory where you don't also have PCMK_schema_directory set is something that doesn't happen all that often.

That should work - the whole point of that block is basically to check if we're running from a source checkout and if so, set the right schema directory. I bet running this from a source directory where you don't also have PCMK_schema_directory set is something that doesn't happen all that often.

My guess as to why this stopped working is that the API key you use to link github and copr is only good for 180 days and then must be regenerated.

I can see how this might be handy to someone, but it's never come up for me.

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.

Re: content, be aware that Pacemaker currently strips text nodes from the CIB. That can be changed but it's possible that certain code (for example, related to XML private data being non-NULL) is relying on the assumption of no text nodes in the CIB. Also be careful that whitespace-only text nodes don't cause problems.

Inform Fabio when it's fixed