[Darshan-users] Bug in dxt_analyzer.py

[François Trahay]

Hi,

(Apologies if you have received multiples copies, my previous email was 
marked as spam on this mailing list)


I am currently using darshan on a single machine and I configured 
darshan-runtime  with the "--with-jobid-env=NONE" option. When running 
dxt_analyzer.py on a darshan file generated with this setup, the script 
crashes because there's no jobid field in the trace:

$ ../install/bin/dxt_analyzer.py -i 
ftrahay_bt.W.9.mpi_io_full_id7207_12-12-58557-3741856262788818305_1.darshan
Traceback (most recent call last):
   File "../install/bin/dxt_analyzer.py", line 287, in <module>
     title = str(jobid)+'_'+action+'_activity'
NameError: name 'jobid' is not defined


Applying the attached patch fixes the problem.

François



-------------- next part --------------
diff --git a/darshan-util/dxt_analyzer.py b/darshan-util/dxt_analyzer.py
index 18b761e..bbfa194 100755
--- a/darshan-util/dxt_analyzer.py
+++ b/darshan-util/dxt_analyzer.py
@@ -260,6 +260,7 @@ with open(dxt_logname) as infile:
     finfo_dict = {}
     curr_fname = ''
     logdata = []
+    jobid="NO_JOBID"
     for line in infile:
         curr_fname, data, flag = parse_dxt_log_line(line, curr_fname, finfo_dict)
         if flag == -11: