Bumping default iozone version to 508

[malucius-rh]

Description

This bumps the default version of IOzone installed by the wrapper from 3.490 (dated and not marked "stable" upstream) to 3.508 (current stable release). There are no changes to wrapper logic or output or usage of iozone itself.

Before/After Comparison

Before: If no iozone exists on the test system the wrapper will install version 3.490.
After: If no iozone exists on the test system the wrapper will install version 3.508

Clerical Stuff

This closes #60
Relates to JIRA: RPOPC-920

Logs iozone_490_to_508.txt

[qodo-code-review]

Review Summary by Qodo

Update default IOzone version to 3.508

✨ Enhancement

Walkthroughs

Description

• Updates default IOzone version from 3.490 to 3.508
• Installs current stable release instead of dated version
• No changes to wrapper logic or functionality

Diagram

flowchart LR
  A["IOzone Wrapper"] -- "Install default version" --> B["iozone3_508<br/>Current Stable"]
  C["iozone3_490<br/>Dated Version"] -.->|replaced| B

Loading

File Changes

1. iozone/iozone_run.sh ⚙️ Configuration changes +1/-1

Bump default IOzone version to 3.508

• Updates iozone_kit variable from iozone3_490 to iozone3_508
• Changes default IOzone version installed when not present on system
• No modifications to wrapper logic or output behavior

iozone/iozone_run.sh

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

[frival]

LGTM, but in the spirit of putting useful stuff in the PR I'd really like to see before and after output from the test. Extra eyes on test output changes are useful to spot things the developer missed, and we've been bitten too many times in the past to not ask for those test artifacts rather than just "I tested it".

[malucius-rh]

LGTM, but in the spirit of putting useful stuff in the PR I'd really like to see before and after output from the test. Extra eyes on test output changes are useful to spot things the developer missed, and we've been bitten too many times in the past to not ask for those test artifacts rather than just "I tested it".

They're coming, I couldn't find the ones I did before so I'm getting fresh and didn't bother marking "draft."

[frival]

Thanks for the logs, it all LGTM now.