Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

results summarizer is broken since 4.1.45

Aperta
  • Qualcosa non va?
#481 3 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@pgmpablo157321 ci sta già lavorando.

Dal 8/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

After compliance check adds scaling factors, the summarizer won't print out the summarized results since v4.1.44. Issue occurs after checking out branch at 4.1.45 commits or newer commits, but summarizer works as expected on the same results path when using the prior v4.1.44 commits as shown below.

This issue prevents any recent MLPerf Training results to display when checking submissions.

When running the mlperf logging verify script from v4.1.45 or later versions on the v6.0 results, you don't get the detailed summarized output, you only see the following:

logging]$ git checkout 782506cc6df92d08660e91d6734a086b5480c8da
Previous HEAD position was 77699df Increment version to 4.1.44
HEAD is now at 782506c Increment version to 4.1.45
logging]$ ./scripts/verify_for_v6.0_training.sh ../training_results_v6.0/Lambda

            ** Detailed log output is also at package_checker.log
             NOTICE: Applying scaling factor 1.0311762501465556 to dir ../training_results_v6.0/Lambda/results/gb300_n18_ngc25.09_nemo/gpt_oss_20b
             Strong Scaling Scores:
             INFO - Running repository checks.
             INFO - Running git-unfriendly file name checks.
             INFO - Running large file checks.
             INFO - ALL CHECKS PASSED.

When using the mlperf logging verify scripts from v4.1.44 on the v6.0 training results, you get this output for the Lamda results (which is expected):

logging]$ git checkout 77699dfa13df58fe9fa541f409b23b2b963b7be0
Previous HEAD position was 782506c Increment version to 4.1.45
HEAD is now at 77699df Increment version to 4.1.44
logging]$ ./scripts/verify_for_v6.0_training.sh ../training_results_v6.0/Lambda

               ** Detailed log output is also at package_checker.log
              NOTICE: Applying scaling factor 1.0311762501465556 to dir Lambda/results/gb300_n18_ngc25.09_nemo/gpt_oss_20b
              Strong Scaling Scores:
              division     availability submitter                          system  \
              0   closed  Available cloud    Lambda  Lambda-1-Click-Cluster_B200_n1
              1   closed  Available cloud    Lambda                Lambda_GB300_n18

              number_of_nodes       host_processor_model_name  host_processors_count  \
              0               1  Intel(R) Xeon(R) Platinum 8570                      2
              1              18                     Neoverse-V2                     36

              accelerator_model_name  accelerators_count  \
              0  NVIDIA Blackwell GPU (B200-SXM-180GB)                   8
              1     NVIDIA Blackwell Ultra GPU (GB300)                  72

              framework       notes  llama31_8b  dlrm_dcnv2  flux1  \
              0  PyTorch NVIDIA Release 25.04  B200 1000W   85.263156         NaN    NaN
              1  PyTorch NVIDIA Release 25.09               11.585940         NaN    NaN

              llama2_70b_lora  llama31_405b  gpt_oss_20b  deepseekv3_671b  \
              0              NaN           NaN    96.457092              NaN
              1              NaN           NaN    18.359156              NaN
                                                                                            details_url  \
              0    https://github.com/mlcommons/training_results_v6.0/blob/main/Lambda/systems/b200_n1_ngc25.09_nemo.json
              1  https://github.com/mlcommons/training_results_v6.0/blob/main/Lambda/systems/gb300_n18_ngc25.09_nemo.json

                                                                       code_url
              0  https://github.com/mlcommons/training_results_v6.0/blob/master/Lambda/benchmarks
              1  https://github.com/mlcommons/training_results_v6.0/blob/master/Lambda/benchmarks
              INFO - Running repository checks.
              INFO - Running git-unfriendly file name checks.
              INFO - Running large file checks.
              INFO - ALL CHECKS PASSED.
Lingua principale
Python
Stelle
43
Fork
60
Merge medio
2g 14h
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di mlcommons/logging

Tutte le issue di mlcommons/logging

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.