Closed cdelzotti closed 1 week ago
This is in the CSV export. Could you printf at line 703 all_results_df and x_df ? It's hard to judge the problem without the shape of your experiment.
Here is a CSV dump of these two variables before it crashed :
,build,test_index,Method,TAG,CPU,WL,TIME,GEN_THREADS,GEN_BURST,GEN_RX_THREADS,GEN_FLOWSIZE,SLEEP_MODE,SLEEP_DELTA,BURST_SIZE,GEN_LENGTH,FREQ,LIMIT,RATE_PER_CORE,GEN_RATE,FIRST_CPU,NUMA_NODE,FASTCLICK_PATH,NPF_TESTIE_PATH,PCI,LIMIT_TIME,LATENCY,LAT00,LAT01,LAT50,LAT95,LAT99,LAT999,LAT100,TESTTIME,RCVTIME,THROUGHPUT,COUNT,BYTES,SENT,DROPPED,DROPPEDPC,TX,TXPPS,PPS,WATT,RAM,POLL_TIME,C1_TIME,C1E_TIME,C6_TIME,TOTAL_CIDLE,run_index
0,local,0,IPFilterDenyPMP,"""test_throughput""",2,1000,10,8,8,8,32,no_sleep,1,32,64,3000,1000000000,4000000,4000000,0,0,/root/fastclick_sleep_modes/,/root/power/,0000:18:00.1,14,750.947289885,20.5,326.125,801.0,832.875,869.5,1540.25,8505.75,14.0131726265,17.033125,3558462711.65,86096460.0,5510174528.0,136424360.0,50327900.0,0.368906989925,5527071021.38,7850961.90256,5054666.46973,44.734199,7.73698,0.0,0.0,0.0,0.0,0.0,0
,build,test_index,Method,TAG,CPU,WL,TIME,GEN_THREADS,GEN_BURST,GEN_RX_THREADS,GEN_FLOWSIZE,SLEEP_MODE,SLEEP_DELTA,BURST_SIZE,GEN_LENGTH,FREQ,LIMIT,RATE_PER_CORE,GEN_RATE,FIRST_CPU,NUMA_NODE,FASTCLICK_PATH,NPF_TESTIE_PATH,PCI,LIMIT_TIME,LATENCY,LAT00,LAT01,LAT50,LAT95,LAT99,LAT999,LAT100,TESTTIME,RCVTIME,THROUGHPUT,COUNT,BYTES,SENT,DROPPED,DROPPEDPC,TX,TXPPS,PPS,SLEEP_MODE,WATT,RAM,POLL_TIME,C1_TIME,C1E_TIME,C6_TIME,TOTAL_CIDLE,run_index
0,local,1,IPFilterDenyPMP,"""test_throughput""",2,1000,10,8,8,8,32,hr_plus,1,32,64,3000,1000000000,4000000,4000000,0,0,/root/fastclick_sleep_modes/,/root/power/,0000:18:00.1,14,743.056567814,29.125,298.5,796.875,832.625,882.625,1543.5,6543.875,14.0132513046,16.93525,3562380694.47,85696774.0,5484595584.0,135642680.0,49945906.0,0.368216744169,5526335457.01,7849926.83813,5060191.01004,5.0,44.508492,7.715913,56.0,134.0,0.0,0.0,190.0,0
The problem might be related to the fact that there are two columns called 'SLEEP_MODE' in x_df
Update : Turned out a dependency I used actually happened to print a 'RESULT-SLEEP_MODE'
without warning, therefore causing a duplicated column. It could be interesting to have a clearer message in npf indicating that a particular column is present multiple times :smiley:
Normally duplicated results get mixed. By default there will be two results per run, which should be fine. You can also add result_add={SLEEP_MODE} in the config so the resutls are additionned instead of duplicated.
Maybe the problem comes from SLEEP_MODE not being numeric? Or one of them is empty?
SLEEP_MODE was actually both a numeric value and a label because of my dependency messing with my script. But it works like a charm now.
Can you help me reproduce the problem ? python3 npf-run.py --test integration/warnmultiple.npf --csv local.csv --force-retest
integration/warnmultiple.npf:
%variables
TEST={A,B,C}
%script
echo "RESULT-TEST 78"
echo "RESULT-TEST MODE
Definitely there is multiple warnings that should happen and I'll work on that, but I don't have a crash.
Result is :
index,build,test_index,TEST,TEST,run_index
0,local,0,A,78.0,0
1,local,0,A,78.0,1
2,local,0,A,78.0,2
3,local,1,B,78.0,0
4,local,1,B,78.0,1
5,local,1,B,78.0,2
6,local,2,C,78.0,0
7,local,2,C,78.0,1
8,local,2,C,78.0,2
Warnings to add :
Fixed in last push. There are now warnings to prevent this situation.
I'm currently trying to run this command :
python3 /usr/local/bin/npf-run.py local --test ./script.npf --graph-filename ./results/graph.pdf --variables LIMIT_TIME=14 --cluster client=$CLIENT server=$SERVER --graph-size 12 10 --single-output ./results/out.csv --cluster-autosave --result-path ./results/
With the following variables in script.npf :
While the (in my case very long) testing happens without any issue, npf crashes afterwards during what seems to be the plotting phase. This is the python stack that appears :
Is there a solution to that problem ? :smiley: