We removed network_test a few months back.
Please update to the latest repo.
http://www.gem5.org/Garnet_Synthetic_Traffic

On Feb 4, 2017, at 4:19 PM, Jason Lowe-Power 
<[email protected]<mailto:[email protected]>> wrote:

Hello,

This is probably a bug in the network test config file. This is not a script 
that is run very often, so I wouldn't be surprised at all if there was 
something wrong.

The error you're seeing is occurring somewhere in the Python configuration 
files. I think it's happening before gem5's simulation starts (before the 
m5.simulate() call). I would try inserting some print statements in the file 
configs/example/ruby_network_test.py and any other python files it references 
to try to figure out where the error is occurring. gdb can also be helpful in 
these situations, but the error may be in the Python code, which makes using 
gdb much harder.

Cheers,
Jason

On Sat, Feb 4, 2017 at 5:36 AM Yogendra Gupta 
<[email protected]<mailto:[email protected]>> wrote:

Hi,

I have run this command.

./build/ALPHA_Network_test/gem5.opt configs/example/ruby_network_test.py  \
  --num-cpus=16 --num-dirs=16 --topology=Mesh --mesh-rows=4  \
 --sim-cycles=1000 \
 --injectionrate=0.01 \
 --synthetic=0 \
 --fixed-pkts \
 --maxpackets=1 \
 --garnet-network=fixed

I am getting an error like:

SystemError: NULL result without error in PyObject_Call

Although as per Gem5 Documentation I have installed all the tools updated 
version.

Kindly suggest how we can resolve this issue?



Thank you

--
With regards,
Yogendra Kumar Gupta

_______________________________________________
gem5-users mailing list
[email protected]<mailto:[email protected]>
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
[email protected]<mailto:[email protected]>
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to