point maintainers to failing test results

[orbeckst]

When the registry raises an issue for my kit and pings me then I would want to have a link to failing test results.

At the moment I have no idea where to look in order to find out what I should actually be fixing (see #152 (comment) ).

[IAlibay]

Unfortunately the GH Python API just isn't that versatile, I had a solution at some point which uses the REST API but it's very flaky.

We could add docs to tell folks where to look at things though?

[orbeckst]

Yes, just pointing to where to go next would be useful.

…

On Jul 7, 2024, at 10:54 AM, Irfan Alibay ***@***.***> wrote: Unfortunately the GH Python API just isn't that versatile, I had a solution at some point which uses the REST API but it's very flaky. We could add docs to tell folks where to look at things though?

[fiona-naughton]

I'm planning to add this when I add to the maintaining-a-kit docs; but to make sure I'm getting this right - I was able to find the current failing tests by going to the latest cron run (on https://github.com/MDAnalysis/MDAKits/actions/workflows/gh-ci-cron.yaml) and looking under "Annotations" on the Summary page (clicking on a result there sometimes takes me right to the error message, and sometimes I have to expand 'run-tests' manually and look through). @IAlibay, is this the best way to direct people, or is there something else?

(PS - looks like Irfan did fix the initial issue for propkatraj, but 'latest' is still failing since the fix hasn't made it's way to a release yet)