Disable GHArchive benchmarks to unblock perf reference in CI #5729
Conversation
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
joseph-isaacs
added
changelog/fix
joseph-isaacs
approved these changes
Dec 15, 2025
Signed-off-by: Adam Gutglick <adam@spiraldb.com>
AdamGS
force-pushed
the
adamg/disable-gharchive-temporarily
branch
from
f6b9b7b to
816271d
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
paultiq
pushed a commit
to paultiq/vortex
that referenced
this pull request
Dec 17, 2025
…data#5729) The current failures of GHArchive is making the reference be stale (over a month old), this PR just stops running them so we can get more up to date results, and I'll sync with @a10y once he's back about the issue/timeline Signed-off-by: Adam Gutglick <adam@spiraldb.com>
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.
The current failures of GHArchive is making the reference be stale (over a month old), this PR just stops running them so we can get more up to date results, and I'll sync with @a10y once he's back about the issue/timeline