Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use workstage name from XML rather than generic names in logs #128

Closed
agama opened this issue Oct 21, 2013 · 3 comments
Closed

Use workstage name from XML rather than generic names in logs #128

agama opened this issue Oct 21, 2013 · 3 comments
Labels
Milestone

Comments

@agama
Copy link

agama commented Oct 21, 2013

The workstage name given in the XML should be used in place of the Sn name in the system log and should be added to the associated records generated in any csv files.

Our XML is dynamically generated, based on user defined parameters, which can result in varying numbers of 'pre-test' write steps to configure the object store environment. These results are typically ignored, but without the user defined step names in the system log and the csv files it is difficult to write a generalised programme to extract and report on only the 'real test' data from the run.

@gilmcgrath
Copy link

Adding a null comment so I can track as a participant

@ywang19
Copy link
Contributor

ywang19 commented Oct 24, 2013

new logic for creating stage id will be as following:

if name is set; then
      use the name
else
      use "s" plus stage index
fi

it's expected to be included in upcoming 0.3.3.0 final release

@ywang19
Copy link
Contributor

ywang19 commented Oct 24, 2013

Just realize one issue with above logic, if people used duplicated stage name, above logic will cause csv file rewrite. so finally, I will keep stage identifier as "s" plus stage index plus stage name, and the identifier will be used in log, stage file (sxxx.csv) and summary file (wxxx.csv).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants