[Benchmarks] remove force rebuild path and unify installdir use

[lslusarczyk]

Defining whether project use install dir is in one place - GitProject constructor, not in configure and needs_rebuild arguments which was error prone. No force rebuild path any more.

"--no-rebuild" option to devops/scripts/benchmarks/main.py is removed and the behavior of the script is the same as previously was with that option. This simplifies the code

Previously --no-rebuild option caused compute-benchmarks, llama , etc... dependent project to be not rebuild if already compiled in proper version (commit hash hardcoded in benchmarks scripts matches).

Now this behavior is default and the only one.

if suite is enabled by options (--sycl, --ur, etc..), compiled and its tag (e.g. compute-benchmarks tag) matches benchmarks's hardcoded one - it is not rebuild, otherwise it is rebuild.

In CI simply workdir is cleaned before running main.py, so previous behavior is preserved.

During manual work, if one wants to force a rebuild a dependent repo he/she needs to remove its binary dir from workdir.

[Copilot]

Pull Request Overview

This PR simplifies the benchmark rebuild logic by removing the --no-rebuild option and consolidating the decision of whether to use an install directory into the GitProject constructor. Previously, rebuild behavior was controlled through multiple mechanisms (force_rebuild, check_install, check_build parameters), which was error-prone. Now, the system automatically skips rebuilds when a project's compiled artifacts exist and its version matches the expected commit hash.

Key changes:

• Removed --no-rebuild CLI option and options.rebuild flag
• Replaced force_rebuild parameter with use_installdir in GitProject constructor
• Simplified needs_rebuild() to check either install or build directory based on use_installdir
• Removed install_prefix parameter from configure() method
• CI now cleans workdir before running to ensure clean builds

Reviewed Changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
devops/scripts/benchmarks/git_project.py	Refactored GitProject to use use_installdir flag, simplified needs_rebuild() and configure() methods
devops/scripts/benchmarks/options.py	Removed rebuild option field
devops/scripts/benchmarks/main.py	Removed --no-rebuild argument and related assignment
devops/scripts/benchmarks/utils/compute_runtime.py	Updated calls to remove check_install parameter and install_prefix argument; added use_installdir=False for compute-runtime
devops/scripts/benchmarks/benches/*.py	Updated benchmark classes to use use_installdir=False and removed install_prefix arguments
devops/scripts/benchmarks/benches/velocity.py	Removed manual build directory cleanup logic
devops/scripts/benchmarks/README.md	Removed documentation about --no-rebuild option
devops/actions/run-tests/benchmark/action.yml	Added workdir cleanup before running benchmarks

[lslusarczyk]

Benchmark changes tested in: https://github.com/intel/llvm/actions/runs/18593660864/job/53014846090

[PatKamin]

Benchmark changes tested in: https://github.com/intel/llvm/actions/runs/18593660864/job/53014846090

Please, run benchmarks with a broader set of suites, not only Compute Benchmarks: preset: Normal

[lslusarczyk]

Benchmark changes tested in: https://github.com/intel/llvm/actions/runs/18593660864/job/53014846090

Please, run benchmarks with a broader set of suites, not only Compute Benchmarks: preset: Normal

https://github.com/intel/llvm/actions/runs/18595652579

[PatKamin]

Actually, a comment that scripts try to reuse binaries or rebuild projects automatically would be useful.

[lslusarczyk]

applied