Does notification timeout still work?

[danrue]

Does the Notification timeout setting still work? I've troubleshot twice lately builds that aren't finishing that should. In both cases, it was due to environments that had previously been submitted no longer being submitted. In such a case, a build never finishes. Setting all environments (including no longer used envs) to "0 expected test runs" does solve the problem for future builds, but old builds will be left spinning hopelessly forever with no way to 'finish'.

In other words, to be more succinct:

• It's easy to get builds that never finish
• Notifications don't seem to be going out after the notification timeout when builds aren't finished
• There's no way to force a build to be finished (is there?)
• This is caused when an environment that was submitted in the past but is no longer being submitted
• The only workaround I know of is to go set all 'expected test runs' in all environments to 0 manually

Example: https://qa-reports.linaro.org/android-lkft/aosp-master-tracking/ Before build 1130, I went in and set expected test runs to 0 for all environments, and then build 1130 got "finished".

[mwasilew]

I'm able to reproduce this problem pretty easily with 'fake' backend. Debugging now. Once fixed it should be possible to add 'integration' tests to cover this case.