Step 3: Checking on the Status of Your Job
Was this helpful?
Was this helpful?
After having deployed the job, we now can use the CLI for the interaction with the network. The jobs were sent to the public demo network, where it was processed and we can call the following functions. The job_id will differ for every submission.
You can find out more information about your job by using .
Let's take a look at the results of the command execution in the terminal:
This outputs all information about the job, including stdout, stderr, where the job was scheduled, and so on.
After the download has finished you should see the following contents in the results directory.
Each of these files contain the following information:
exitCode - the numeric exit code after your job ran (just like if you ran looked at the exit code on your local machine)
Here are few resources that provide a deeper dive into running jobs with Bacalhau:
After the job runs, if it produces any output, the output will be stored according to the setting for your job. You can download your job results directly by using .
Depending on selected , this may result in:
outputs - a directory of everything you wrote in the job (if using ).
stderr - the output of the stream of the job.
stdout - the output of the stream of the job.
And that's it! If you'd like to go to the next level, you can - it's super easy too!
, ,