Open jdm opened 6 years ago
This is a symptom of other bugs (e.g. the try bug), or when you synchronize on a restart while there are existing builds.
I think I saw this most recently since the try bug should have been fixed and after we were done restarting and synchronizing, but I'll keep an eye out.
This has happened multiple times in the past three days.
This causes multiple builds to be started but only the most recent one matters. The older duplicate ones are ignored but still consume resources.