Hi Nilay, It was due to the typo in HMC.py. Should be resolved with your latest push.
Andreas On 05/11/2015, 11:37, "gem5-dev on behalf of Nilay Vaish" <gem5-dev-boun...@gem5.org on behalf of ni...@cs.wisc.edu> wrote: >On Thu, 5 Nov 2015, Cron Daemon wrote: > >> ***** >>build/ALPHA/tests/opt/quick/se/00.hello/alpha/linux/simple-timing-ruby >>FAILED! >> ***** >>build/ALPHA/tests/opt/quick/se/00.hello/alpha/tru64/simple-timing-ruby >>FAILED! >> ***** >>build/ALPHA/tests/opt/quick/se/50.memtest/alpha/linux/memtest-ruby >>FAILED! >> ***** >>build/ALPHA/tests/opt/quick/se/60.rubytest/alpha/linux/rubytest-ruby >>FAILED! >> ***** >>build/ALPHA_MOESI_hammer/tests/opt/quick/se/50.memtest/alpha/linux/memtes >>t-ruby-MOESI_hammer FAILED! >> ***** >>build/ALPHA_MOESI_hammer/tests/opt/quick/se/60.rubytest/alpha/linux/rubyt >>est-ruby-MOESI_hammer FAILED! >> ***** >>build/ALPHA_MOESI_hammer/tests/opt/quick/se/00.hello/alpha/tru64/simple-t >>iming-ruby-MOESI_hammer FAILED! >> ***** >>build/ALPHA_MOESI_hammer/tests/opt/quick/se/00.hello/alpha/linux/simple-t >>iming-ruby-MOESI_hammer FAILED! >> ***** >>build/ALPHA_MESI_Two_Level/tests/opt/quick/se/50.memtest/alpha/linux/memt >>est-ruby-MESI_Two_Level FAILED!***** >>build/ALPHA_MESI_Two_Level/tests/opt/quick/se/00.hello/alpha/linux/simple >>-timing-ruby-MESI_Two_Level FAILED!***** >>build/ALPHA_MESI_Two_Level/tests/opt/quick/se/60.rubytest/alpha/linux/rub >>ytest-ruby-MESI_Two_Level FAILED! >> ***** >>build/ALPHA_MESI_Two_Level/tests/opt/quick/se/00.hello/alpha/tru64/simple >>-timing-ruby-MESI_Two_Level FAILED! >> ***** >>build/ALPHA_MOESI_CMP_directory/tests/opt/quick/se/00.hello/alpha/linux/s >>imple-timing-ruby-MOESI_CMP_directory FAILED! >> ***** >>build/ALPHA_MOESI_CMP_directory/tests/opt/quick/se/00.hello/alpha/tru64/s >>imple-timing-ruby-MOESI_CMP_directory FAILED! >> ***** >>build/ALPHA_MOESI_CMP_directory/tests/opt/quick/se/60.rubytest/alpha/linu >>x/rubytest-ruby-MOESI_CMP_directory FAILED! >> ***** >>build/ALPHA_MOESI_CMP_directory/tests/opt/quick/se/50.memtest/alpha/linux >>/memtest-ruby-MOESI_CMP_directory FAILED! >> ***** >>build/ALPHA_MOESI_CMP_token/tests/opt/quick/se/00.hello/alpha/tru64/simpl >>e-timing-ruby-MOESI_CMP_token FAILED! >> ***** >>build/ALPHA_MOESI_CMP_token/tests/opt/quick/se/00.hello/alpha/linux/simpl >>e-timing-ruby-MOESI_CMP_token FAILED!***** >>build/ALPHA_MOESI_CMP_token/tests/opt/quick/se/60.rubytest/alpha/linux/ru >>bytest-ruby-MOESI_CMP_token FAILED!***** >>build/ALPHA_MOESI_CMP_token/tests/opt/quick/se/50.memtest/alpha/linux/mem >>test-ruby-MOESI_CMP_token FAILED! >> ***** >>build/MIPS/tests/opt/quick/se/00.hello/mips/linux/simple-timing-ruby >>FAILED! >> ***** >>build/SPARC/tests/opt/quick/se/00.hello/sparc/linux/simple-timing-ruby >>FAILED! >> ***** >>build/X86/tests/opt/quick/se/00.hello/x86/linux/simple-timing-ruby >>FAILED! >> ***** >>build/X86/tests/opt/quick/fs/10.linux-boot/x86/linux/pc-simple-timing >>CHANGED! > > >Not sure what's going on wrong with these ruby regressions. They run >fine >on my machine. Someone with access to zizzer should take a look. > >-- >Nilay >_______________________________________________ >gem5-dev mailing list >gem5-dev@gem5.org >http://m5sim.org/mailman/listinfo/gem5-dev ________________________________ -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ gem5-dev mailing list gem5-dev@gem5.org http://m5sim.org/mailman/listinfo/gem5-dev
