-
Notifications
You must be signed in to change notification settings - Fork 103
Improve the time series api + add policy for regression #7156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
multiSearchAnyCaseInsensitive(arch, {arch: Array(String)}) | ||
OR empty({arch: Array(String)}) | ||
) | ||
ORDER BY branch, timestamp, commit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Order by commit is weird, as it's just a random hash. Do you mean sorted by workfflow_id
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can remove this, think timstamp is enough
aws/lambda/benchmark_regression_summary_report/common/benchmark_time_series_api_model.py
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed mainly the SQL queries and found a minor issue there. The rest LGTM I guess
For API:
add listCommits api
For regression lambda