Custom Query (101 matches)
Results (97 - 99 of 101)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #39 | fixed | Wrong number of free nodes reported | bastiaans | aloga@… |
| Description |
When there are more jobs than CPUs on a system, the JobMonarch? web interface reports a negative number of Free CPUS. Replacing on the overiew.php file the lines 698 and 699 with the lines below should correct the problem. 698 $free_nodes = ($avail_nodes - $running_nodes) >= 0 ? $avail_nodes - $running_nodes : 0; 699 $free_cpus = ($avail_cpus - $running_cpus) >= 0 ? $avail_cpus - $running_cpus : 0; Cheers. |
|||
| #26 | fixed | stop_timestamp is not correct when only one job run. | bastiaans | alexis.michon@… |
| Description |
When a job run alone on the cluster, stop_timestamp save in the database isn't correct. Same job on the same cluster has a correct stop_timestamp when there is at least one other job running at the same time. |
|||
| #27 | fixed | wrong display in web frontend | bastiaans | alexis.michon@… |
| Description |
When we set $COLUMN_NODES to 1 in conf.php, the column node (in the web frontend) isn't filled correctly. In search.php, the variable which contains the nodes is not reset between each iteration and the first job is displayed with 1 node, the second with two, the third with three, etc... Patch is attached |
|||
