-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Filter out more expected errors from sccache log #56281
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
Filter out more expected errors from sccache log #56281
Conversation
💊 CI failures summary and remediationsAs of commit 951e017 (more details on the Dr. CI page): ✅ None of the CI failures appear to be your fault 💚
❄️ 1 failure tentatively classified as flakybut reruns have not yet been triggered to confirm:
|
@samestep has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
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.
Seems like any time sccache appears in the logs it's basically useless to devs (especially when Dr. CI picks it up), should we skip outputting its logs altogether (or somehow shove them somewhere where you have to go looking for them to get it)?
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.
looks good.
RE: Test plan: since we only added one string to the list, it should be fine
It is useful to debug whether there's any issue regarding build time regression. no necessarily for a failure though |
Co-authored-by: Rong Rong <walterddr.walterddr@gmail.com>
@samestep has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
Summary: This PR extends `.jenkins/pytorch/print_sccache_log.py` to filter out a distracting "error" message that walterddr came across while debugging failures in pytorch#55176: ``` =================== sccache compilation log =================== ERROR 2021-04-05T15:44:18Z: sccache::server: Compilation failed: Output { status: ExitStatus(ExitStatus(256)), stdout: "", stderr: "/var/lib/jenkins/.cache/torch_extensions/test_compilation_error_formatting/main.cpp: In function ‘int main()’:\n/var/lib/jenkins/.cache/torch_extensions/test_compilation_error_formatting/main.cpp:2:23: error: expected ‘;’ before ‘}’ token\n int main() { return 0 }\n ^\n" } ``` Pull Request resolved: pytorch#56281 Test Plan: TODO (reviewers: is there an easy way to test this?) Reviewed By: walterddr Differential Revision: D27826064 Pulled By: samestep fbshipit-source-id: 7322a830c1246820a5b2b7bbeaa4697ebd13b617
This PR extends
.jenkins/pytorch/print_sccache_log.py
to filter out a distracting "error" message that @walterddr came across while debugging failures in #55176:Test plan:
TODO (reviewers: is there an easy way to test this?)