Advanced: CSV Regression Job Import

For advanced flows, Simscope Regressions can be imported in comma-separated-value CSV format.

NOTE: most flows should use the simpler JSON format instead, but CSV can be useful for higher performance applications.

CSV file format

CSV is a simple text format, using commas (,) to separate each field. Each record is delimited by a newline (\n).

If any field value contains commas or whitespace, surround the value with a quote before and after (").

Example: "This is my quoted CSV value"

The first line of the CSV file is a header line, which tells Simscope which fields will be submitted in the CSV, and in which order.

Example: category,time,jobnum

Using CSV vs JSON for Simscope

In general, you should use JSON job imports via the Tunnel, but advanced flows may desire to directly bulk import using the CSV format.

Note that the Tunnel internally automatically converts JSON inputs to CSV outputs.

Job CSV Fields

You can import any field listed in Job Fields reference.

Example Job CSV File

This CSV contains 4 job records, and 1 header line (5 lines total).

Note: the timestamps are in RFC-3339 format.

category,time,build,testgroup,path,userid,config,host,seed,result,exitcode,runtimems,simcycles,message,bucket,classification,metadata
compile,2020-02-27T11:42:04.0Z,2core,mytestgroup,/home/runs/myregr/1/compile,,make -j4 OPT=1,compute-1,,pass,0,64224,0,,,,
sim,2020-02-28T00:27:05.203377517Z,2core,directed,/home/runs/myregr/1/job-6,,runme --seed 5,compute-12,,fail,100,6170,85,"foo bar, This is my error: 5",,,
sim,2020-02-28T00:26:14.7544Z,mybuild,mytestgroup,/home/runs/myregr/1/job-1,,runme --seed 0,compute-12,,,0,0,0,,,,
sim,2020-02-28T00:29:24.2Z,1core,smoke,/home/runs/myregr/1/job-8,,runme --seed 7,compute-12,,fail,100,8638,119,CYCLE timeout after 200 cycles,,,transactions:102

Importing CSV files into Simscope

CSV files can be published via Tunnel (RabbitMQ), or via REST-API calls.

Simscope Administration Guide