Improve assert failure message in test_get_torch_func_signature_exhaustive#67039
Improve assert failure message in test_get_torch_func_signature_exhaustive#67039pearu wants to merge 4 commits intogh/pearu/8/basefrom
Conversation
…stive [ghstack-poisoned]
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit 06e2877 (more details on the Dr. CI page):
🕵️ 2 new failures recognized by patternsThe following CI failures do not appear to be due to upstream breakages:
|
| Job | Step | Action |
|---|---|---|
| Test | 🔁 rerun |
This comment was automatically generated by Dr. CI (expand for details).
Follow this link to opt-out of these comments for your Pull Requests.Please report bugs/suggestions to the (internal) Dr. CI Users group.
CI Flow Status⚛️ CI FlowRuleset - Version:
You can add a comment to the PR and tag @pytorchbot with the following commands: # ciflow rerun, "ciflow/default" will always be added automatically
@pytorchbot ciflow rerun
# ciflow rerun with additional labels "-l <ciflow/label_name>", which is equivalent to adding these labels manually and trigger the rerun
@pytorchbot ciflow rerun -l ciflow/scheduled -l ciflow/slowFor more information, please take a look at the CI Flow Wiki. |
|
It is odd that this test appears to be failing on unrelated PRs today and the error message on for those failures is very cryptic -- @jamesr66a or @Chillee do you know what's up? |
…ature_exhaustive" cc mruberry [ghstack-poisoned]
…ature_exhaustive" cc mruberry [ghstack-poisoned]
|
@mruberry The explanation for the failing tests is given here: #67088 (comment) . Basically, |
…ature_exhaustive" cc mruberry [ghstack-poisoned]
|
@cpuhrsch has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
Stack from ghstack:
cc @mruberry
Differential Revision: D31899719