Jobs

A Job (sometimes called a Fail) is a single instance of a Signature.

Jobs are the smallest unit of tracking within Simscope, and can have either a pass or fail result.

• Each Regression is composed of 1 or more Jobs.
• Each Signature is composed of 1 or more Jobs.
• Users can Comment on Jobs.

NOTE: Simscope currently only tracks completed jobs.

Jobs can be searched within a Signature.

Job Metadata

Jobs contain a variety of metadata fields, used to both launch the job, and the results of the job:

• Raw Error Message (message)
• Regression Name
• Signature # (NOTE: this is a calculated field upon import)
• Timestamp (when the job was launched)
• Build target
• Config/plusargs
• Seed
• Result (pass/fail)
• Runtime
• Cycles
• Hostname
• Custom job metadata fields
  • See the Admin Guide for Custom Job Metadata docs.

State

Simscope also tracks internal State Data of each job:

• State name
• Assignee
• Issue

Job State can be updated manually or via Rules.

Simscope tracks both *Global state of signatures (ie merged across all jobs in a signature), and Filtered state (tracked across a batch of jobs).

• For examle, a component can have a signature as FIXED, while the overall signature is OPEN (globally).

Job Activity (History)

Simscope tracks history on job state changes, to enable auditing and debugging of job history:

• User that updated the job.
• Timestamp of the update.
• New state of the job.
• optional comment by the user.

Example Jobs

Custom metadata

Simscope can optionally store arbitrary integer, floating point, and string metadata fields for each job.