Re: [Gems-users] regarding tester


Date: Thu, 06 Oct 2005 13:44:32 -0400
From: "Salil..." <smpant@xxxxxxxx>
Subject: Re: [Gems-users] regarding tester
hi
I am running the deterministic tester ( the RANDOMIZATION variable is set to false & deterministic driver set to true). Actually I dont know whether its done or not It seems to be writing into the trace file and I can also see the End System configuration print messages.Also I tried running the tester on one of the protocols thats already been provided, MOSI_SMP_bcast, and it doesent seem to finish also (actually how long does the tester take to finish?).
this is how I am running the tester
./tester_exec -l10000 -cNqc -p4 -a1 -vlow
regarding my previous question. I wanted to know whether the tester has some timeouts for responses, to catch cases where requests are stalled forever .
thanks
salil


Bradford Beckmann wrote:

Salil,

What tester are you running?  By default the tester runs the random
action-check pair test, but other test are also available.  The reason I
ask is that some of the DETERMINISTIC_TESTER tests have not been fully
debugged and may rely on some assumptions that are causing it from failing
to complete.

However, if you are not running the deterministic_tester, there is
probably something wrong with you protocol.  Often "tester not completing"
problems occur when there are reoccurring events on the eventqueue.  The
tester only completes when all events have been issued from the
eventqueue.  I would suggest printing out the eventqueue to ensure it is
empty at the end of the tester run.

There are currently no tests for dropped messages.

Brad



On Thu, 6 Oct 2005, Salil... wrote:



Hi
   I am using tester for checking a coherence protocol that I have
written. I ran the tester with length (-l) 10000 onwards and verbosity low
The tester doesent seem to end -  it just hangs somewhere like this (
actually this is true for all lengths)
------------------------------------------
Debug: in fn bool CacheMemory<ENTRY>::tryCacheAccess(const Address&,
CacheRequestType, DataBlock*&) [with ENTRY = L1Cache_Entry] in
system/CacheMemory.h:290: address is [0xfc0, line 0xfc0]
Request trace file closed.
---------------------------------------
The trace file size (ruby.trace.gz) is 0.
however if I dont supply the -v option, it ends like this
-----------------------------------
================ End System Configuration Print ================

Testing clear stats...Done.
Request trace enabled to output file 'ruby.trace.gz'
---------------------------------------
It just hangs after this and so i have to kill it.
is that something to do with my protocol or am i not running the tester
rite ?
also.,my concern here is that I want to catch situations where the
messages never make it back ( becoz of incorrect design etc ) and so
some requests get stalled forever. Does the tester catch situations like
these ???
thanks
salil
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users




-----------------------------------------------------------------
Department of Computer Science Residence
University of Wisconsin
1210 W. Dayton St. #6366 608 Eagle Heights Apt. L
Madison, WI 53706 Madison, WI 53705
(608)265-2702 (608)852-6133
-----------------------------------------------------------------
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users



[← Prev in Thread] Current Thread [Next in Thread→]