Bug #6306
Updated by Tom Clegg almost 9 years ago
h2. summary
When a pipeline fails, it stops updating its own cache of job status. However, some jobs may continue to run. In such cases, Workbench displays either up-to-date job status or out-of-date job status, depending on whether the current user has permission to look up the jobs themselves. This is confusing.
h2. implementation
When displaying a pipeline instance _that is not Running_, if the cached job state is not already Failed or Complete, and Workbench fails to look up the current state, it should
* show a "current job state not available" message
* fade out or completely hide the cached state
h2. initial bug report
on my admin account where I ran the pipeline in the home directory, I have https://cloud.curoverse.com/pipeline_instances/qr1hi-d1hrv-pkxdm18hmf8jsht (bcosc@curoverse)
!instance_nosync.png!
I copied it over to the Making BWA faster project and when I went on my non-admin account: (bcosc@bu.edu) I have
https://cloud.curoverse.com/pipeline_instances/qr1hi-d1hrv-pkxdm18hmf8jsht
!instance_nosync2.png!
when I click on the instance from bcosc@bu.edu, the time that samtools-merge is running for changes but not to the time that I waited to click on it. Also, there are no busy nodes, so it doesn't seem like it is actually running.