Skip to content

Fixbench#4928

Merged
soulomoon merged 18 commits into
haskell:masterfrom
soulomoon:fixbench
May 9, 2026
Merged

Fixbench#4928
soulomoon merged 18 commits into
haskell:masterfrom
soulomoon:fixbench

Conversation

@soulomoon
Copy link
Copy Markdown
Collaborator

@soulomoon soulomoon commented May 6, 2026

fix #4929

@soulomoon soulomoon added CI Continuous integration performance Issues about memory consumption, responsiveness, etc. labels May 6, 2026
@soulomoon soulomoon marked this pull request as ready for review May 7, 2026 11:54
@soulomoon soulomoon requested review from fendor and michaelpj as code owners May 7, 2026 11:54
Copy link
Copy Markdown
Collaborator

@fendor fendor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me, but can you explain from a high level view what has changed now? Are we no longer generating the visualisations for the memory usage?

Comment thread .github/workflows/bench.yml Outdated
Comment thread shake-bench/shake-bench.cabal Outdated
Comment thread cabal.project Outdated
hs-source-dirs: bench
build-tool-depends:
haskell-language-server:ghcide-bench,
eventlog2html:eventlog2html,
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we not using eventlog2html anymore to generate the graphs?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

profiled runs still emit raw .hp, we are just not generate the graphs so we can decouple from its deps.

Co-authored-by: fendor <fendor@users.noreply.github.com>
@soulomoon
Copy link
Copy Markdown
Collaborator Author

soulomoon commented May 8, 2026

Three things have been done.

  1. enhence the checking before benchmark, ensure the target repo actually buildable and the targets file actually exist.
  2. we no longer generating the visualisations for the memory usage.
  3. bump ghc and cabal version and update the target repos.

The benchmark actually been broken for the 9.12 for a couple of months for the target repo lsp. So instead of leaving the benchmark stale and no one actually use it and no one pay attention to it. We leave just enough functionalities for our CI.

@soulomoon soulomoon merged commit f158128 into haskell:master May 9, 2026
60 of 62 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Continuous integration performance Issues about memory consumption, responsiveness, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Keep benchmark CI up to date

2 participants