2.0 - Pavilion Variables

[pflarr]

Pavilion provides a set of variables that should be system independent, and are usable in test configurations. Additionally, Pavilion automatically includes a number of environment variables that are set in every script.

'pav' variables

• user - the current user running the test.
• hostname - The current nodename. The cluster name is provided under 'system' vars.
• when - The datetime, in local time, broken out into the following components:
  • .str - A human readable date/time string.
  • .strtz - A human readable date/time string with time zone.
  • .day, .month, .year, .hour, .minute, .sec, .ms, .dayofweek, .tz
  • .epoch - The epoch time.
• when_utc - As per when, but in utc.
• Note that the when times all refer to the time the test was kicked off, not when it actually ran.
• pav_config_dirs - The directories that pavilion uses to contain configurations, in resolution order.
• pav_run_dir - The Pavilion installation directory.
• pav_working_dir - The root directory of where pav will build and run tests.
• pav_version - The current version of pavilion, with .full, .major, .minor, .release components.

Pav environment vars.

These are primarily for information that can only be known after a test config has been resolved. Additionally, the ability to add variables via the overall Pavilion config should be provided.

• PAV_WORKING_DIR - The test working directory.
• PAV_BUILD_DIR - The build directory.

[nicholas-sly]

Shouldn't PAV_RESULTS_DIR be in the post-resolution set as well?