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.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Yesterday
Wed, Jan 8
Tue, Jan 7
Dec 17 2024
Dec 4 2024
Nov 20 2024
Nov 14 2024
Nov 12 2024
I can see how this might be handy to someone, but it's never come up for me.
Nov 4 2024
Oct 31 2024
Oct 14 2024
Oct 2 2024
Sep 25 2024
Sep 23 2024
Sep 18 2024
Sep 11 2024
Aug 20 2024
Aug 8 2024
Jul 24 2024
Jul 20 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.
Jul 9 2024
Jul 3 2024
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.
Jun 14 2024
Jun 4 2024
May 31 2024
May 15 2024
May 14 2024
May 13 2024
May 7 2024
May 6 2024
May 1 2024
Mar 28 2024
Mar 26 2024
Mar 19 2024
Feb 1 2024
Jan 30 2024
Jan 26 2024
Inform Fabio when it's fixed