Changes

# Job - The smallest unit of work shown in Treeherder's main UI. This can be a build job or a test job. Each test job can run many tests within it, but they get reported as a group to Treeherder. Examples of these would be the Windows 8 x64 Debug build job, or a mochitest-browser-chrome-1 test job.  Each push to a repository will run a number of build jobs for various platforms (Linux, MacOS, Windows, Android). Most platforms will make multiple builds in various configurations: OPT (optimized builds that strip out information helpful for debugging failuresin favor of making things faster), DEBUG (unoptimized builds that don't strip out the debugging information), and [https://en.m.wikipedia.org/wiki/Profile-guided_optimization PGO ] (the build compiler process runs through the code a few times, taking longer to complete, but speeding up some code paths to make the build run fasterthan Opt builds) then . Then those builds will each be used to run a number of test jobs to verify that the compiled code is running as intended. Then either a build or test job runs into trouble, the job is reported as a failure to Treeherder, needing to be classified (also called 'starred' at Mozilla, since classifying a job marks the job as classified by adding a star next to the job symbol inTreeherder by the current sheriff on duty (that's you!).