jobs
--jobsv1.6.0Converts `jobs` command output to JSON
LinuxmacOSFreeBSDcommand
$ cat input.txt | jc-rs --jobsA real pair
From the reference corpus (ubuntu-18.04/jobs.json). The left pane is the input the fixture ships; the right pane is the corpus's expected JSON. CI compares jc-rs with it field by field under the published differential. Hover a value to see where it came from.
jobsubuntu-18.04
[1] Running sleep 11 & [2] Running sleep 12 & [3]- Running sleep 13 & [4]+ Running sleep 14 &
expected outputjson
Use the Left and Right arrow keys to highlight the matching value in the input.
[ { "job_number": 1, "status": "Running", "command": "sleep 11 &" }, { "job_number": 2, "status": "Running", "command": "sleep 12 &" }, { "job_number": 3, "history": "previous", "status": "Running", "command": "sleep 13 &" }, { "job_number": 4, "history": "current", "status": "Running", "command": "sleep 14 &" } ]
Fixture coverage
2/2oracle-valid pairs match under the published structural JSON comparison
Magic syntax
not availableThis parser reads a file or a string rather than a command, so there is nothing for jc-rs to run. Pipe it in.
Source: crates/jc-rs-parsers/src/system/jobs.rs. jc-rs targets the schemas defined by the original Python tool. Fixture coverage above is the measured evidence for this parser; test the inputs your pipeline depends on. Compare