Skip to content

Conversation

@kdvalin
Copy link
Member

@kdvalin kdvalin commented Jan 12, 2026

Description

Instead of using fragile regular expression logic to validate test results, pydantic allows for much more maintainable methods.

Presently the validation looks for:

  • iteration > 0
  • threads > 0
  • IterationsPerSec > 0.0 (can't be NaN or inf)

Before/After Comparison

Before

Validation code was using regular expressions, which are hard to maintain and liable to breaking in ways hard to understand.

After

Validation code uses pydantic, which is much simpler and easier to understand.

Clerical Stuff

Closes TBD

Relates to JIRA: RPOPC-<TICKET_NUMBER>

CSV Output

# Test general meta start
# Test: coremark
# Results version: v1.01
# Host: --sys_type
# Sys environ: None
# Tuned: tuned_none
# OS: 6.18.3-200.fc43.x86_64
# Numa nodes: 1
# CPU family: AMD Ryzen 7 PRO 7840HS w/ Radeon 780M Graphics
# Number cpus: 16
# Memory: 64420248kB
# Test general meta end
iteration:threads:IterationsPerSec
1:16:352578.228294
1:16:376323.010584

Run log

coremark.log

Instead of using fragile regular expression logic to validate test
results, pydantic allows for much more maintainable methods.

Presently the validation looks for:
- iteration > 0
- threads > 0
- IterationsPerSec > 0.0 (can't be NaN or inf)
@kdvalin kdvalin requested a review from a team January 12, 2026 18:48
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