fix(TEST01): NameError in verify_performance when the loadgen log reports errors

[Anai-Guo]

compliance/TEST01/verify_performance.py::parse_result_log formats a warning with a name that
does not exist in that scope:

    if mlperf_log.has_error():
        print(
            "WARNING: {} ERROR reported in {}".format(
                line.split()[0],        # <- NameError: name 'line' is not defined
                file_path))

$ pyflakes compliance/TEST01/verify_performance.py
compliance/TEST01/verify_performance.py:57:17: undefined name 'line'

line is a leftover from when this file scanned the summary as text — the sibling
compliance/TEST04/verify_performance.py:88 still does exactly that
(error = line.split(" ", 1)[0].strip() inside for line in test_file:). TEST01 was moved to
the parsed MLPerfLog object and the format argument was not moved with it.

The consequence is that TEST01 verification crashes only when the loadgen log actually
reports errors — i.e. precisely the case this warning was written for. On a clean run
has_error() is False and the branch is skipped, which is why it has gone unnoticed.

Replaying parse_result_log (lifted out of the file with ast) against a stub MLPerfLog
for an Offline run whose log reports 3 errors:

### loadgen log reports 3 errors (mlperf_log.has_error() is True)
  [before] NameError: name 'line' is not defined
  [after]  WARNING: 3 ERROR reported in loadgen.txt
           returned ('Offline', 1234.5, None)

Fix

Use the log object's own error count, mlperf_log.num_errors() — the accessor
has_error() is itself defined in terms of (log_parser.py:160), and the one used for this
exact message everywhere else in the repo:

• tools/submission/log_parser.py:214 — "- Number of errors: {:d}".format(mlperf_log.num_errors())
• tools/submission/submission_checker/checks/performance_check.py:168
• tools/submission/submission_checker/checks/accuracy_check.py:276

This keeps the rendered message identical in shape to TEST04's
("WARNING: " + error + " ERROR reported in ...").

🤖 Generated with Claude Code

[github-actions]

MLCommons CLA bot:
Thank you very much for your submission; we really appreciate it. Before we can accept your contribution,
we ask that you sign the MLCommons CLA (Apache 2). Please submit your GitHub ID to our onboarding form to initiate
authorization. If you are from a MLCommons member organization, we will request that you be added to the CLA.
If you are not from a member organization, we will email you a CLA to sign. For any questions, please contact
support@mlcommons.org.
0 out of 1 committers have signed the MLCommons CLA.
❌ @Anai-Guo
_{You can retrigger this bot by commenting recheck in this Pull Request}