Closed Bug 1262295 Opened 8 years ago Closed 8 years ago

build-central is stale

Categories

(Webtools Graveyard :: DXR, defect)

defect
Not set
major

Tracking

(firefox48 affected)

RESOLVED FIXED
Tracking Status
firefox48 --- affected

People

(Reporter: nthomas, Assigned: fubar)

References

()

Details

https://dxr.mozilla.org/build-central/search?q=release_channel_mapping should return results like http://hg.mozilla.org/build/buildbot-configs/file/default/mozilla/config.py#l2545. It appears that repo is stuck on a rev from Feb 21 (5f9a37958eaf). Similarly build/buildbotcustom is on 6035a0b57bfb from Feb 19. Please investigate.
Indexing by hand now. Two issues to investigate: one is jenkins throwing a 'FATAL: String index out of range: -1' which we've seen but haven't found a cause or fix, and second is why it hasn't even tried indexing in a month (surely changes have been made to build repos since then).
Assignee: nobody → klibby
Indexing done, at least.
(In reply to Kendall Libby [:fubar] from comment #1)
> Indexing by hand now. Two issues to investigate: one is jenkins throwing a
> 'FATAL: String index out of range: -1' which we've seen but haven't found a
> cause or fix, and second is why it hasn't even tried indexing in a month
> (surely changes have been made to build repos since then).

this might need further poking as it seems it wasn't a one off. build-central, at least buildbot-configs, hasn't been updated since april 13th. :(
Hey fubar, any idea what's happening here? not critical/blocking so please help only when time permits.
Flags: needinfo?(klibby)
there's an issue within one (or more!) of the jenkins plugins that's causing the build-central and nss projects to not run. I haven't forgotten about it but it's fairly low prio to fix atm. OTOH, doing the build manually is pretty easy (and Callek pinged me in #static to ask for just that this morning). It's up to date again.
Flags: needinfo?(klibby)
might be related but if you click on 'permalink' button on right sidebar from within a build-central based repo, you get a 500.
Handling for repo 'collections' has been rewritten: jenkins no longer polls all of the SCMs and insteads just builds on a schedule like it/MXR used to, so it no longer gets stuck on the MultiSCM index out of bounds error.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.