ninja-build/ninja

Add a performance test script / "performance regression tests"

Open

#1,733 建立於 2020年2月6日

在 GitHub 查看
 (4 留言) (0 反應) (0 負責人)C++ (10,194 star) (1,544 fork)batch import
help wanted

描述

Currently this is done manually by building Chromium before and after a commit. I think it would be good to have a script, which you can pass two commit hashes and a path to a Chromium source, which will then compare the -d stats result.

Maybe add the functionality to misc/measure.py?

See https://github.com/ninja-build/ninja/pull/1577#issuecomment-517797439

貢獻者指南

技術棧
cpppython
領域
testingperformancebuild system
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
PythonNinja build system conceptsBasic understanding of performance testing
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Extend the existing misc/measure.py script to accept two commit hashes and a Chromium source path. The script should build with ninja for each commit and compare the ` d stats` output. Reference the discussion in PR #1577 (comment) for context on the desired comparison logic. The deliverable is a script that automates the manual performance regression check.
Add a performance test script / "performance regression tests" · ninja-build/ninja#1733 | Good First Issue