-
Notifications
You must be signed in to change notification settings - Fork 5
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
[CHORE] Land or retire rewrite-lockfile.js for registry-lockfile warmups
enhancementNew feature or requestNew feature or requestStatus: Open.#163 In vltpkg/benchmarks;[CHORE] Retain raw benchmark artifacts for 90 days
enhancementNew feature or requestNew feature or requestStatus: Open.#161 In vltpkg/benchmarks;[BUG] Test whether Babylon registry-clean results depend on registry run order
bugSomething isn't workingSomething isn't workingStatus: Open.#162 In vltpkg/benchmarks;[CHORE] Choose an outlier-resistant statistic for benchmark charts
enhancementNew feature or requestNew feature or requestStatus: Open.#160 In vltpkg/benchmarks;[BUG] Fail registry-lockfile benchmarks when warmup does not create a lockfile
bugSomething isn't workingSomething isn't workingStatus: Open.#159 In vltpkg/benchmarks;[BUG] Honor workflow_dispatch filters in matrix include entries
bugSomething isn't workingSomething isn't workingStatus: Open.#157 In vltpkg/benchmarks;[BUG] Do not publish push-triggered benchmark runs to gh-pages
bugSomething isn't workingSomething isn't workingStatus: Open.#158 In vltpkg/benchmarks;[CHORE] Decide whether to render or remove per-package registry data
enhancementNew feature or requestNew feature or requestStatus: Open.#156 In vltpkg/benchmarks;[BUG] Use total-time data for the registry history chart’s seconds axis
bugSomething isn't workingSomething isn't workingStatus: Open.#154 In vltpkg/benchmarks;[BUG] Make the registry leaderboard summary meaningful across fixtures
bugSomething isn't workingSomething isn't workingStatus: Open.#155 In vltpkg/benchmarks;[BUG] Preserve partial benchmark failures instead of publishing survivor-only stats
bugSomething isn't workingSomething isn't workingStatus: Open.#153 In vltpkg/benchmarks;- Status: Open.#142 In vltpkg/benchmarks;