Stefano Charissis
Stefano Charissis
Also see the new "Flakiness Report", FYI https://github.com/ethereum-optimism/optimism/pull/16411 Note that we also include the "Job Name" here, which tells us which backend was used and may give us more clues...
### Why SLAs/SLOs Make Sense 1. Clear expectations; engineering teams know what to expect from CI performance 2. Accountability; Platforms team has measurable targets to optimize against 3. Objective metrics;...
# CI Pipeline SLAs & Accountability Framework ## Service Level Agreements ### **Availability & Performance** - **Job Success Rate**: 95% (excluding legitimate test failures) - **PR Feedback Time**: 80% of...
Seeking feedback on the above. Especially if there's any irrelevant metrics that we can remove. We wish to close this out before the end of the week.
Thank you very much for the feedback all! I like the idea of "getting smarter about how we allow new tests into the repo". We've previously discussed potentially introducing a...
Will not implement CI SLAs for now; closing.
It appears the build is failing due to auth issues only? @kurtosis-tech/engineers, @tedim52 - I believe this is ready for review.
Hey @tedim52 , let me know if you have any questions on this or if I can help progress it in any way.
> Prior art here may be all we need https://github.com/flashbots/contender Specifically https://github.com/flashbots/contender/issues/145
Most of the flakiness has nothing to do with acceptance testing - it's things like CircleCI machine issues, networking issues, infra issues.