Skip to content

warnings from darshan-job-summary.pl when autoperf APMPI data is present #12

@carns

Description

@carns

The darshan-job-summary.pl tool produces output that looks like this if executed on a darshan log with Autoperf APMPI data present:

Use of uninitialized value $str in substitution (s///) at /home/carns/working/install/lib/TeX/Encode.pm line 137, <PARSE_OUT> line 467.
Use of uninitialized value $str in substitution (s///) at /home/carns/working/install/lib/TeX/Encode.pm line 138, <PARSE_OUT> line 467.
Use of uninitialized value $str in substitution (s///) at /home/carns/working/install/lib/TeX/Encode.pm line 139, <PARSE_OUT> line 467.
Use of uninitialized value $str in substitution (s///) at /home/carns/working/install/lib/TeX/Encode.pm line 140, <PARSE_OUT> line 467.
...

I'm getting over 2,000 lines similar to that when running it on a single process mpi-io benchmark log.

It looks like the issue is that the Autoperf parsed output does not have the same number of columns as other Darshan modules, in particular the file name, mount pt, and fs type fields are missing. It looks like there are also warnings later due to some counters having string rather than numeric values.

I'm not sure what the best fix is; either APMPI (and other Autoperf modules if they have the same problem, I haven't checked the others) needs to add dummy columns to the output or darshan-job-summary.pl should be modified to skip AP records.

This problem is peculiar to darshan-job-summary since it is using perl to parse string output from darshan parser, but we need to fix it until the Python tools are mature enough to deprecate it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions