Closed Bug 744958 Opened 12 years ago Closed 12 years ago

we download updateSUT.py to updateSUT.py.x, then execute updateSUT.py

Categories

(Release Engineering :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Assigned: Callek)

Details

Attachments

(1 file)

========= Started Download updateSUT.py (results: 0, elapsed: 0 secs) (at 2012-04-11 09:35:49.877641) =========
python /builds/tegra-101/test/tools/buildfarm/utils/retry.py -s 1 -r 5 -t 1260 wget --no-check-certificate http://hg.mozilla.org/build/tools/raw-file/eba35f2aeabd/sut_tools/updateSUT.py
 in dir /builds/tegra-101/test/build (timeout 1320 secs)
 watching logfiles {}
 argv: ['python', '/builds/tegra-101/test/tools/buildfarm/utils/retry.py', '-s', '1', '-r', '5', '-t', '1260', 'wget', '--no-check-certificate', 'http://hg.mozilla.org/build/tools/raw-file/eba35f2aeabd/sut_tools/updateSUT.py']
 environment:
  PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
  PWD=/builds/tegra-101/test/build
  SUT_IP=10.250.49.89
  SUT_NAME=tegra-101
  __CF_USER_TEXT_ENCODING=0x1F5:0:0
 closing stdin
 using PTY: False
retry: Calling <function run_with_timeout at 0x10050c230> with args: (['wget', '--no-check-certificate', 'http://hg.mozilla.org/build/tools/raw-file/eba35f2aeabd/sut_tools/updateSUT.py'], 1260, None, None, False, True), kwargs: {}, attempt #1
Executing: ['wget', '--no-check-certificate', 'http://hg.mozilla.org/build/tools/raw-file/eba35f2aeabd/sut_tools/updateSUT.py']
--2012-04-11 09:35:49--  http://hg.mozilla.org/build/tools/raw-file/eba35f2aeabd/sut_tools/updateSUT.py
Resolving hg.mozilla.org (hg.mozilla.org)... 10.2.74.153
Connecting to hg.mozilla.org (hg.mozilla.org)|10.2.74.153|:80... connected.
HTTP request sent, awaiting response... 200 Script output follows
Length: 3193 (3.1K) [text/x-python]
Saving to: `updateSUT.py.5'

     0K ...                                                   100% 56.4M=0s

2012-04-11 09:35:50 (56.4 MB/s) - `updateSUT.py.5' saved [3193/3193]

program finished with exit code 0
elapsedTime=0.326884
========= Finished Download updateSUT.py (results: 0, elapsed: 0 secs) (at 2012-04-11 09:35:50.229022) =========

========= Started Running updateSUT.py failed (results: 5, elapsed: 7 mins, 30 secs) (at 2012-04-11 09:35:50.229899) =========
python updateSUT.py 10.250.49.89
 in dir /builds/tegra-101/test/build (timeout 1200 secs)
 watching logfiles {}
 argv: ['python', 'updateSUT.py', '10.250.49.89']
 environment:
  PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
  PWD=/builds/tegra-101/test/build
  SUT_IP=10.250.49.89
  SUT_NAME=tegra-101
  __CF_USER_TEXT_ENCODING=0x1F5:0:0
 closing stdin
 using PTY: False
Traceback (most recent call last):
  File "updateSUT.py", line 95, in <module>
    sys.exit(main(sys.argv[1]))
  File "updateSUT.py", line 12, in main
    ver = version(dm)
  File "updateSUT.py", line 69, in version
    ver = dm.sendCMD(['ver']).split("\n")[0]
  File "/builds/tegra-101/test/build/devicemanagerSUT.py", line 148, in sendCMD
    raise DMError("unable to connect to %s after %s attempts" % (self.host, self.retrylimit))        
devicemanager.DMError: unable to connect to 10.250.49.89 after 5 attempts
INFO: updateSUT.py: Connecting to: 10.250.49.89
reconnecting socket
unable to connect socket
reconnecting socket
unable to connect socket
reconnecting socket
unable to connect socket
reconnecting socket
unable to connect socket
reconnecting socket
unable to connect socket
reconnecting socket
unable to connect socket
program finished with exit code 1
elapsedTime=450.394462
========= Finished Running updateSUT.py failed (results: 5, elapsed: 7 mins, 30 secs) (at 2012-04-11 09:43:20.652246) =========
Assignee: nobody → bugspam.Callek
Component: Release Engineering → Release Engineering: Automation (General)
QA Contact: release → catlee
This should make it always overwrite instead of append .X this does not however clear up existing foopie dir's. I figured automating that cleaning would help now, but be a pain later when dealing with our code.
Attachment #614574 - Flags: review?(bear)
Attachment #614574 - Flags: review?(bear) → review+
this went live in today's reconfig
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: