![[Buildbot Logo]](/chrome/site/header-text-transparent.png)
Ticket #1980 (closed defect: fixed)
updateBigStatus not called enough?
| Reported by: | dustin | Owned by: | dustin |
|---|---|---|---|
| Priority: | blocker | Milestone: | 0.8.7 |
| Version: | master | Keywords: | database |
| Cc: |
Description
I'm looking at the metabuildbot's builders right now, and it says every builder is offline - yet all of the buildslaves are online.
Also, os-win7 says it's building in the builders page, but on the builder (singular) page, it does not appear to be building anything.
Change History
comment:2 Changed 2 years ago by Dustin J. Mitchell
- Status changed from new to closed
- Resolution set to fixed
call bldr.updateBigStatus more often
This should fix "stale" status appearing in various status displays - Fixes #1980.
Changeset: c892a85b9b8b11a4841788828b88248e447e7f79
comment:3 Changed 14 months ago by dustin
- Status changed from closed to reopened
- Resolution fixed deleted
- Milestone changed from 0.8.4 to 0.8.7
This is definitely not fixed -- the metabuildbot is showing a whole bunch of yellow right now, even though nothing is happening.
comment:4 Changed 14 months ago by dustin
- Owner set to dustin
- Status changed from reopened to assigned
I think this needs a serious overhaul of the code tracking this state.
comment:5 Changed 14 months ago by tom.prince
I wonder if we should be tracking this state, or just calculating it as needed?
comment:6 Changed 13 months ago by Dustin J. Mitchell
Work around incorrect big status
This just calls updateBigStatus every 30m, which should at least keep things in a consistent state long-term. Refs #1980.
Changeset: 445c7e9059e8c235eec73754b0ac6ec161cf5fe4
comment:7 Changed 13 months ago by Dustin J. Mitchell
Work around incorrect big status
This just calls updateBigStatus every 30m, which should at least keep things in a consistent state long-term. Refs #1980.
Changeset: 058a5c2cab2f90c0e399bec45933d8489d914096
comment:8 Changed 13 months ago by Dustin J. Mitchell
Work around incorrect big status
This just calls updateBigStatus every 30m, which should at least keep things in a consistent state long-term. Refs #1980.
Changeset: 445c7e9059e8c235eec73754b0ac6ec161cf5fe4
comment:9 Changed 13 months ago by Dustin J. Mitchell
Work around incorrect big status
This just calls updateBigStatus every 30m, which should at least keep things in a consistent state long-term. Refs #1980.
Changeset: 058a5c2cab2f90c0e399bec45933d8489d914096
comment:10 Changed 12 months ago by dustin
- Milestone changed from 0.8.7 to 0.8.+
Let's see if this is still bad in 0.8.7.
comment:11 Changed 3 months ago by dustin
- Status changed from assigned to closed
- Resolution set to fixed
- Milestone changed from 0.8.+ to 0.8.7
Seems improved. At any rate, it goes away in nine.
calling updateBigStatus via manhole is enough to synchronize the state.