Closed Bug 1175391 Opened 9 years ago Closed 8 years ago

[B2G][BUILD] Flame-kk v2.2 user build contains marionette server

Categories

(Taskcluster :: General, defect)

Product:
Taskcluster
Component:
General
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: wachen, Unassigned)

Details

Build ID               20150616162504
Gaia Revision          3414b07dc489976bf510fd8042c0af3b1192c160
Gaia Date              2015-06-16 22:04:56
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/a2db74491088
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150616.195206
Firmware Date          Tue Jun 16 19:52:17 EDT 2015
Bootloader             L1TC100118D0

127|shell@flame:/ $ netstat                                                    
Proto Recv-Q Send-Q Local Address          Foreign Address        State
 tcp       0      0 0.0.0.0:2828           0.0.0.0:*              LISTEN
 tcp       0      0 0.0.0.0:666            0.0.0.0:*              LISTEN

We found that there is marionette server in user build for flame-kk lately. This is a critical issue.
Component: Releases → General Automation
QA Contact: rail → catlee
Component: General Automation → TaskCluster
Product: Release Engineering → Testing
QA Contact: catlee
Component: TaskCluster → General
Product: Testing → Taskcluster
wander, do you have any insight into this?
Flags: needinfo?(wcosta)
(In reply to Greg Arndt [:garndt] from comment #1)
> wander, do you have any insight into this?

Why is this a TC issue? AFAIK, v2.2 is done by buildbot. There is bug 1174336 to add it, but iirc, the last talk was that v2.2 and v2.1 builds would shutdown soon so not worth the trouble. I think :RyanVM and :nhirata_ were looking into that.
Flags: needinfo?(wcosta)
No updates, so marking invalid given that this build was in buildbot.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.