Closed
Bug 767426
Opened 13 years ago
Closed 13 years ago
update the sutagent to 1.09
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Assigned: Callek)
Details
we have a handful of bugs that have been checked into sutagent in the tree. We need to work on rolling this out in production.
I have a copy of the sutagent1.09 built on my people account: http://people.mozilla.org/~jmaher/sutagent/
If we can take 1.09 and get it in staging, verify it, then roll out to production that would be fantastic.
Updated•13 years ago
|
Assignee: nobody → bugspam.Callek
Assignee | ||
Comment 1•13 years ago
|
||
[root@relengweb1.dmz.scl3 mobile]# wget http://people.mozilla.org/~jmaher/sutagent/SUTAgentAndroid1.09.apk
[root@relengweb1.dmz.scl3 mobile]# mv SUTAgentAndroid1.09.apk sutAgentAndroid.1.09.apk
And then edited updateSUT.py on foopy06, (which is staging with my "don't need buildbot to updateSUT explicitly" change [happens in verify instead, which is still run in buildbot though].
So I'll stage this for a few days/over the weekend.
Assignee | ||
Comment 2•13 years ago
|
||
Ok, so foopy06 is either failling to install 1.09 OR has a wrong internal version.
Jeff who is by far not an android expert attempted to install this manually and got:
│android-sdk-linux/platform-tools/adb install SUTAgentAndroid1.09.apk
1173 KB/s (62136 bytes in 0.051s)
pkg: /data/local/tmp/SUTAgentAndroid1.09.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Then he tried with it removed and then reinstalled:
│android-sdk-linux/platform-tools/adb install -r SUTAgentAndroid1.09.apk
1153 KB/s (62136 bytes in 0.052s)
pkg: /data/local/tmp/SUTAgentAndroid1.09.apk
Failure [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES]
Reporter | ||
Comment 3•13 years ago
|
||
ok, the .apk I had didn't have the version number bumped, now it is bumped officially to 1.09. As for the install_failed_* messages that jhammel saw, those happen when you have conflicting packages (watcher, fencp, ffxcp). I am sure there are other reasons. I tested this with updateSUT and it worked fine.
Please give: people.mozilla.org/~jmaher/sutagent/SUTAgentAndroid1.09.apk, a new try as I just uploaded it.
Assignee | ||
Comment 4•13 years ago
|
||
(In reply to Joel Maher (:jmaher) from comment #3)
> ok, the .apk I had didn't have the version number bumped, now it is bumped
> officially to 1.09. As for the install_failed_* messages that jhammel saw,
> those happen when you have conflicting packages (watcher, fencp, ffxcp). I
> am sure there are other reasons. I tested this with updateSUT and it worked
> fine.
>
> Please give: people.mozilla.org/~jmaher/sutagent/SUTAgentAndroid1.09.apk, a
> new try as I just uploaded it.
Just uploaded to the build server, overwriting the old copy of 1.09 I added.
And started clientproxy on foopy06 with the 1.09 version specified
Reporter | ||
Comment 5•13 years ago
|
||
can we close this bug out?
Assignee | ||
Comment 6•13 years ago
|
||
..apparently not, just learned that I didn't actually update it (never checked in the version change to tools) Will do so tonight when I re-attempt deploying
Assignee | ||
Comment 7•13 years ago
|
||
Assignee | ||
Comment 8•13 years ago
|
||
This was done on the 28'th
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•