Rohan Bhaumik

@shepherdjay thanks for trying Automated test selection. I've referenced this in a new issue. Let's continue the discussion there https://github.com/codecov/codecov-ats/issues/30

@eXpl0it3r you're right, the 250 Codecov uploads per rolling 30 shouldn't apply for a public repo. I've flagged this for review with our support team

@eXpl0it3r - how many uploads are you making on the same commit?

ok got it... and are you seeing this ``` debug - 2024-04-10 06:27:11,134 -- Upload result --- {"result": "RequestResult(error=RequestError(code='HTTP Error 429', params={}, description='{\"detail\":\"Request was throttled.\"}'), warnings=[], status_code=429, text='{\"detail\":\"Request was throttled.\"}')"}...

Thanks for your feedback @houserx-jmcc - we're looking into adding support for reporting on GH Job summary as well Re the issue with EPIPE - yeah it's something we've noticed....

@houserx-jmcc out of curiosity what non PR usecases are you using https://github.com/phoenix-actions/test-reporting for? Off the top of my head, I'd guess something along the lines of running tests before deploy...

@houserx-jmcc - is this directionally what you had in mind? (still early days!) https://github.com/joseph-sentry/codecov-cli/actions/runs/8560172298

@houserx-jmcc - We're currently testing a new version of our test analytics feature internally where we're able to detect and report on Flaky Tests. At this time, I'm reaching out...

thanks @houserx-jmcc. Here are some times that work for us (you can find time beginning next week if that works better) - https://calendar.app.google/7qTT3zeshUnrEHMy5 cc @Adal3n3

@Blacksmoke16 currently yes the following is an accurate way to describe the system > global to a repo and long as I upload all the junit reports it'll just work...