Home > OS >  CPU2017 test CPU
CPU2017 test CPU

Time:09-16

Test for several machine has the following error, it represents what mean? How to change?



# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

# INVALID RUN - INVALID RUN - INVALID RUN - INVALID RUN - INVALID RUN #

# #

# # 'reportable' flag not set during the run

# 471. Omnetpp peak did not have the enough runs! #

# 456. The hmmer peak did not have the enough runs! #

# 445. Gobmk peak did not have the enough runs! #

# 458. Sjeng peak did not have the enough runs! #

# 429. The MCF peak did not have the enough runs! #

# 473. Astar peak did not have the enough runs! #

# 483. Xalancbmk peak did not have the enough runs! #

# 400. Perlbench peak did not have the enough runs! #

# 464. H264ref peak did not have the enough runs! #

# 462. Libquantum peak did not have the enough runs! #

# 401. Bzip2 peak did not have the enough runs! #

# 403. The GCC peak did not have the enough runs! #

# No 'base' runs! The Base measurement required! #

# Error 483. Xalancbmk: 483. Xalancbmk: copy # 0 non - zero return code (rc=254, signal=0) #

# Error 483. Xalancbmk: Output miscompare #

# #

# INVALID RUN - INVALID RUN - INVALID RUN - INVALID RUN - INVALID RUN #

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

CodePudding user response:

Did not have the enough runs!
What's wrong?
  • Related