status attribute indicates the internal disposition of the job; one of the following:
skipped - The job was scheduled but never run, usually because the build was stopped prematurely, due to a user interrupt or a build error in an earlier job.
conflict - Based on filesystem access, the job was determined to have run too early, and so its output and filesystem modifications were discarded. The job will be rerun with the correct filesystem state.
reverted - The job was run but its output and filesystem modifications were discarded. This is subtly
different from "conflict" in that the cause for the revert is not within the job itself, but in an earlier job. For example, this job may have run already when a build error was detected in an earlier job, causing the build to stop prematurely. The results from this job would then be discarded.
rerun - The job is the second attempt at running a job that was previously found to be in conflict.
normal - None of the above; this is the default value.