Closed
Bug 1220743
Opened 9 years ago
Closed 8 years ago
[2.5 updates] tracking - no builds nor FOTA files are listed for 2.5 and 2.6
Categories
(Taskcluster :: General, defect)
Taskcluster
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nhirata, Unassigned)
References
Details
(Keywords: qablocker, Whiteboard: [b2g-balrog])
We had fixed FOTA in 2.5; it's broken for flame since the branching. Please fix.https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-flame-kk/latest/
Reporter | ||
Comment 1•9 years ago
|
||
This blocks contributors from FOTAing and FOTA testing.
Severity: normal → blocker
Keywords: qablocker
Updated•9 years ago
|
Component: General Automation → General
Product: Release Engineering → Taskcluster
QA Contact: catlee
Comment 2•9 years ago
|
||
This is partly due to having no automation at all on 2.5, but also due to having to disable submissions to balrog.
Reporter | ||
Comment 3•9 years ago
|
||
We have no 2.6 recent builds either. Please mark this as highest b2g priority as this blocks QA completely for working on anything relevant on our reference device for both 2.5/2.6.
This broke since friday.
Flags: needinfo?(sdeckelmann)
Summary: FOTA files are not listed for 2.5 and 2.6 → no builds nor FOTA files are not listed for 2.5 and 2.6
Comment 4•9 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #3)
> We have no 2.6 recent builds either. Please mark this as highest b2g
> priority as this blocks QA completely for working on anything relevant on
> our reference device for both 2.5/2.6.
>
> This broke since friday.
Until balrog is re-enabled, I can't do anything.
Flags: needinfo?(sdeckelmann)
Reporter | ||
Updated•9 years ago
|
Reporter | ||
Comment 5•9 years ago
|
||
As far as I know buildbot + balrog are working just fine for the flame...
I apologize; Could you explain the specific issue please? I think I'm missing something.
Flags: needinfo?(sdeckelmann)
Flags: needinfo?(catlee)
Comment 6•9 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #5)
> As far as I know buildbot + balrog are working just fine for the flame...
> I apologize; Could you explain the specific issue please? I think I'm
> missing something.
Balrog access from TaskCluster was disabled for a couple days. It was re-enabled this afternoon.
The link to pvtbuilds is related to Buildbot builds, and automation should be enabled for 2.5 now.
Reporter | ||
Comment 7•9 years ago
|
||
Ok thanks. I saw bug 1220252.
Flame is built on both build systems. Aries is built only on Taskcluster.
We had Flame 2.5 builds; we don't have Aries 2.5 builds at all.
Aries 2.6 builds was blocked by bug 1220252 I think as well?
If we have access this afternoon then we should have 2.6 builds tomorrow? Is that correct?
Reporter | ||
Comment 8•9 years ago
|
||
I'm not sure which other bug is handling Nexus-4-kk and Nexus-5-l FOTA builds. Is there a separate bug for this?
Comment 9•9 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #8)
> I'm not sure which other bug is handling Nexus-4-kk and Nexus-5-l FOTA
> builds. Is there a separate bug for this?
sounds like that's bug 1223259
Depends on: 1223259
Comment 10•9 years ago
|
||
this seems like the meta bug tracking all things updates and 2.5 related.
I'm not sure if we should spin off a separate bug for what's missing with 2.6 but, iiuc, 2.5 is the current priority we are working towards getting right.
Comment 11•9 years ago
|
||
Downgrading to critical as this appears to be a meta bug.
Severity: blocker → critical
Flags: needinfo?(sdeckelmann)
Updated•9 years ago
|
Flags: needinfo?(catlee)
Updated•9 years ago
|
Whiteboard: [b2g-balrog]
Reporter | ||
Comment 12•9 years ago
|
||
I'm fixing nexus 5 and 4 for full fota on master; it doesn't seem like we care so much about 2.5 now that it's about to ship.
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•