perfSONAR User Q&A and Other Discussion

[Brian Candler <>]

On 05/09/2019 13:27, Brian Candler wrote:
> Since I've no idea what to expect here, I can't see if these are right 
> or not; but it seems to me that there's nothing available at the URL 
> with the /result suffix.

Aside: the reason I'm chasing this down is not especially because I want 
to use the "pscheduler result" command.  It's because after fixing my 
previous problem with run_can_proceed(), I find that scheduled 
throughput tests are now running but are not storing results in the 
database.

I can see now that result-merged comes from result_merged column in the 
database, and for this particular run it's null.  There are quite a few 
null:

pscheduler=# select run.state,run_state.enum,run.status,count(*) from 
run join run_state on run_state.id=run.state where result_merged is null 
group by run.state,run_state.enum,run.status;
 state |   enum    | status | count
-------+-----------+--------+-------
     1 | pending   |        |   298
     3 | running   |        |     4
     4 | cleanup   |      0 |     8
     5 | finished  |      0 |     2
     7 | missed    |        |     6
     9 | preempted |      1 |     8
    10 | nonstart  |        |     1
(7 rows)

I can understand it being null for a job which didn't run. However the 
particular run I'm looking at has status 5 which is "finished".

pscheduler=# select id,state,status,result_merged from run where 
uuid='5687f64a-0dd0-49d9-9554-05c48e806723';
  id   | state | status | result_merged
-------+-------+--------+---------------
 24623 |     5 |      0 |
(1 row)

Regards,

Brian.