replace api #7112
Open
replace api #7112
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
This was referenced Sep 6, 2025
meta-cla
bot
added
the
CLA Signed
yangw-dev
added a commit
that referenced
this pull request
Sep 9, 2025
Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom): * #7112 * #7096 * #7095 * __->__ #7094 main class to detect regression 1. use baseline data to generate baseline for regression detection, currently support (max,min, latest, earliest) within the baseline data window 2. decide wether the target data list under the threshold for regression detection based on the baseline value. 3. if detected more than 2 continuous dp from current timestamp, mark as regression
yangw-dev
added a commit
that referenced
this pull request
Sep 10, 2025
Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom): * #7112 * #7096 * __->__ #7095 add logics to write the report to db table
yangw-dev
added a commit
that referenced
this pull request
Sep 10, 2025
Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom): * #7112 * __->__ #7096 * #7095 # Add github notification settings currently we only create github comment if and only a regression status is detected. later we can add if we want to add suspicious too, ## Prerequest currently user must: 1. create a github issue first, and put it in the Policy section to make this work 2. Each issue should be associated with a butterfly rule to link to internal workplace/ oncall emails ## later improvement as you see, currently if a regression does not resolved, it will send notification to github everyday. since we have those report in db, we can later do exponential notification based on previous report status
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stack from ghstack (oldest at bottom):
create a new query for compiler time series fetching api.
two major things here:
New arch values in table
list below is nductor distinct device and arch for Pass 3 month from clickhouse oss_ci_benchmark_torchinductor table
@huydhn I listed question mark for unknown mapping to arch values from output, like those:
