Fix search_cache job cache generation by skipping multi arch payloads#21675
Merged
bwatters-r7 merged 1 commit intoJul 15, 2026
Merged
Conversation
Contributor
Author
|
@bwatters-r7 Thoughts on skipping the MultiArch payloads and removing the cache size from the modified module? |
Contributor
Author
|
I believe the failing Python Meterpreter tests are not related to this change. |
bwatters-r7
approved these changes
Jul 15, 2026
Contributor
|
Before: |
Contributor
|
After |
Contributor
Release NotesFix search_cache job cache generation by skipping multi arch payloads |
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
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.
Description
This PR fixes the CI search_cache generation job.
Previous error:
The payload above supports multiple architectures, so I think it doesn't make sense for it to have a single specific cache size. Also, from the shared specs:
MultiArch payloads can potentially have wildly different cache sizes per-arch. We only have a singular CachedSize constant, so this seems like the right step.
Breaking Changes
None
Verification Steps
Test Evidence
The tool works again.
AI Usage Disclosure
I used AI to help debug the issue.