Conversation
Summary: XNNPACK sometimes calls weight cache look_up_or_insert with ptr==nullptr. This is a bit weird - maybe a bug on the XNNPACK side?, but it seems to do this when it's already hit the cache. Just return the cached value for the key without validating contents in this case, since we can't insert anything. Differential Revision: D97006279
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/18295
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 5 Pending, 2 Unrelated FailuresAs of commit bb64d12 with merge base eb92cec ( NEW FAILURES - The following jobs have failed:
BROKEN TRUNK - The following jobs failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@GregoryComer has exported this pull request. If you are a Meta employee, you can view the originating Diff in D97006279. |
This PR needs a
|
|
@GregoryComer has imported this pull request. If you are a Meta employee, you can view this in D97006279. |
| // since calling look_up_or_insert with ptr==nullptr doesn't really make | ||
| // sense... | ||
| if (ptr == nullptr) { | ||
| return offset; |
There was a problem hiding this comment.
worst case we will return SIZE_MAX?
And we can't continue without ptr from here anyway.
|
Test failures are a coreml-related and portable tolerance check. Bypassing. |
Summary: XNNPACK sometimes calls weight cache look_up_or_insert with ptr==nullptr. This is a bit weird - maybe a bug on the XNNPACK side?, but it seems to do this when it's already hit the cache. Just return the cached value for the key without validating contents in this case, since we can't insert anything.
Differential Revision: D97006279