add action yml to populate issue#7807
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| - name: Checkout code | ||
| uses: actions/checkout@v4 |
Check warning
Code scanning / zizmor
credential persistence through GitHub Actions artifacts Warning
|
Good to go? |
|
Friendly ping @maresb |
maresb
left a comment
maresb
left a comment
There was a problem hiding this comment.
I would have just used pytest-split, which defines pytest --store-durations
But this is a really interesting solution! I'm really intrigued by your idea of collecting the timings in a GH Issue! It solves the DB problem, at least for now.
I suspect you'll hit a character limit at some point.
I have a billion things going on at the moment, but I'm hoping to set up a server sometime soon to receive telemetry like this. As I've mentioned, I'm really interested in using PyMC to do inference on the test times. 😉
Yes, definitely some pros there. We were having that the test_durations didn't stay synced with changing repo and / or the test_durations didn't reflect the times in the CI/CD runs (large imbalance of run times still) This is more manual and gets the github issue interface. Related to pymc-labs/pymc-marketing#2249
Possible, I have looked through many of the logs and I have not hit that yet.
That'd be cool |
|
The github issue comment character limit is 65,536 |
3 participants
Description
Adding the forgotten yml workflow file to populate the issue here: #7686
CC: @ricardoV94
Related Issue
Checklist
Type of change
📚 Documentation preview 📚: https://pymc--7807.org.readthedocs.build/en/7807/