Beaker tracks "reviewed" state for each recipe: there's a check box on the job page, plus we automatically consider a recipe to be reviewed whenever the recipe page is displayed. However if the recipe is not complete yet, then it shouldn't be automatically marked as reviewed when the page is displayed (because not all the results are there yet, so by definition the user can't have fully reviewed it). There is an interesting edge case which is: what if the recipe finishes while the page is open? The page re-fetches the recipe data every 30 seconds so if the page is already open and the recipe finishes the user will see the complete results, which means they could have reviewed it. The page should probably mark the recipe as reviewed at that point.
(In reply to Dan Callaghan from comment #0) > However if the recipe is not complete yet, then it shouldn't be > automatically marked as reviewed when the page is displayed (because not all > the results are there yet, so by definition the user can't have fully > reviewed it). So this part is basically a dupe of bug 1376645, which I seem to have filed and then fixed forgetting that this one was still here. However, the patch for bug 1376645 did not take into account this edge case: > There is an interesting edge case which is: what if the recipe finishes > while the page is open? The page re-fetches the recipe data every 30 seconds > so if the page is already open and the recipe finishes the user will see the > complete results, which means they could have reviewed it. The page should > probably mark the recipe as reviewed at that point. so it would be good to get that fixed too. Let's make this bug about this edge case.
https://gerrit.beaker-project.org/#/c/5752/
Beaker 24.4 has been released.