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.
Metadata
Jobs contain a variety of metadata, used to both run 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 metadata
State
Simscope also tracks internal State Data of each job:
- State name
- Assignee
- Issue
Job State can be updated manually or via Rules.
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
| Category | Build Target | Result | Message |
|---|---|---|---|
compile | - | pass | - |
sim | coverage | pass | - |
sim | default | fail | stack overflow |
sim | default | fail | FIFO exception |
Custom metadata
Simscope can optionally store arbitrary integer, floating point, and string metadata fields for each job.