Skip to content

ci: use FIO packages from ROCm/fio instead of building from source#195

Closed
Copilot wants to merge 1 commit intorildixon/ci-fio-integrationfrom
copilot/sub-pr-185
Closed

ci: use FIO packages from ROCm/fio instead of building from source#195
Copilot wants to merge 1 commit intorildixon/ci-fio-integrationfrom
copilot/sub-pr-185

Conversation

Copy link

Copilot AI commented Feb 26, 2026

Refactors the AIS system testing workflow to consume pre-built FIO packages from the ROCm/fio repository rather than building FIO from source during test execution.

Changes:

  • Add build_FIO job that calls reusable workflow ROCm/fio/.github/workflows/build-fio.yml
  • Download FIO packages (runtime + hipfile engine for Fedora-based distros) as artifacts in run_FIO_tests
  • Install FIO packages via platform package manager instead of configure/make steps
  • Use system fio binary instead of /ais/fio/build/fio
  • Remove FIO repository checkout and build steps from test job
  • Add ldconfig after hipFile package installation to ensure library paths are registered

Platform-specific handling:

  • Rocky: Downloads both fio and fio-engine-hipfile packages (dynamically linked engines)
  • SUSE/Ubuntu: Downloads single fio package (statically linked engines)

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Copilot AI changed the title [WIP] Refactor FIO steps into separate CI job ci: use FIO packages from ROCm/fio instead of building from source Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants