Add slowest test issue CI/CD

[wd60622]

Description

Adding a CI/CD to populate #1124

Related Issue

• Closes #
• Related to #

Checklist

• Checked that the pre-commit linting/style checks pass
• Included tests that prove the fix is effective or that the new feature works
• Added necessary documentation (docstrings and/or example notebooks)
• If you are a pro: each commit corresponds to a relevant logical change

Type of change

• New feature / enhancement
• Bug fix
• Documentation
• Maintenance
• Other (please specify):

---

📚 Documentation preview 📚: https://pytensor--1125.org.readthedocs.build/en/1125/

[wd60622]

A lot more sections than PyMC Marketing... Should I try for some formatting or would shortening the section "summary" still convey the same information?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.10%. Comparing base (231a977) to head (cb4dcec).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1125   +/-   ##
=======================================
  Coverage   82.10%   82.10%           
=======================================
  Files         185      185           
  Lines       48130    48130           
  Branches     8669     8669           
=======================================
  Hits        39519    39519           
  Misses       6444     6444           
  Partials     2167     2167           

[ricardoV94]

We can omit the following:

• python3.10 runs
• float32 runs (no reason these should be slower than the float64)
• The benchmark suite as it doesn't make sense to "speedup" so take that out as well

[wd60622]

We can omit the following:

• python3.10 runs
• float32 runs (no reason these should be slower than the float64)
• The benchmark suite as it doesn't make sense to "speedup" so take that out as well

Done. I've updated the issue with that filter. See how it looks there

[wd60622]

I am looking into adding total time next to each section. I think that would be helpful for summary

[ricardoV94]

just to see if I understand, this reads the times from the GitHub CI logs?

[wd60622]

just to see if I understand, this reads the tones from the GitHub CI looks?

Tones? The issue at the moment will be how it looks every 6 hours

[ricardoV94]

just to see if I understand, this reads the tones from the GitHub CI looks?

Tones? The issue at the moment will be how it looks every 6 hours

reads the times from the GitHub logs. Fat fingers

[wd60622]

reads the times from the GitHub logs. Fat fingers

Correct from the CI job rather than from pytest runs. So there might be some cushion added to that with job spin up, etc

[wd60622]

But gives some ball park estimate of times for each

[wd60622]

Any more feedback @ricardoV94 ?

[ricardoV94]

Thanks @wd60622

[ricardoV94]

My question above wasn' clear. I was confirming this job does not need to run seperate CI tests, but instead simply reads the logs of the existing CI tests