Closed
Bug 748911
Opened 12 years ago
Closed 12 years ago
http://build.mozilla.org/talos/mobile/ unable to load
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: Callek, Assigned: bear)
Details
(Whiteboard: [buildduty])
We download the sutAgentAndroid.*.apk from http://build.mozilla.org/talos/mobile/* And right now I am getting timeouts with
The server at build.mozilla.org is taking too long to respond.
Trying to gather anything from there.
Reporter | ||
Updated•12 years ago
|
Severity: normal → critical
OS: Windows 7 → All
Hardware: x86_64 → All
Assignee | ||
Comment 1•12 years ago
|
||
may be related to relengweb01 work
dustin is exploring in #build now
Whiteboard: [buildduty][downtime][outage]
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → bear
Comment 2•12 years ago
|
||
foopy05:~ cltbld$ wget http://build.mozilla.org/talos/mobile/sutAgentAndroid.1.06.apk
--2012-04-25 12:54:17-- http://build.mozilla.org/talos/mobile/sutAgentAndroid.1.06.apk
Resolving build.mozilla.org (build.mozilla.org)... 10.22.74.128
Connecting to build.mozilla.org (build.mozilla.org)|10.22.74.128|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-04-25 12:54:17 ERROR 404: Not Found.
[root@relengweb1.dmz.scl3 mobile]# pwd
/var/www/html/build/talos/mobile
[root@relengweb1.dmz.scl3 mobile]# ls -al
total 140
drwxr-sr-x 2 armenzg 101 4096 Mar 13 11:42 .
drwxrwsr-x 7 catlee 101 4096 Mar 12 08:15 ..
-rw-r--r-- 1 armenzg 101 15192 Mar 13 11:42 devicemanager.py
-rw-r--r-- 1 armenzg 101 37684 Mar 12 11:51 devicemanagerSUT.py
-rwxr-xr-x 1 armenzg 101 61051 Mar 12 08:16 sutAgentAndroid.1.07.apk
-rw-r--r-- 1 armenzg 101 1841 Mar 12 09:24 updateSUT.new.py
-rw-r--r-- 1 armenzg 101 2085 Mar 12 14:29 updateSUT.py
Assignee | ||
Comment 3•12 years ago
|
||
reducing the priority and removing outage tag as this is VPN related and not downtime related
Severity: critical → normal
Whiteboard: [buildduty][downtime][outage] → [buildduty]
Reporter | ||
Comment 4•12 years ago
|
||
This works from new (scl3) build-vpn, from every machine that needs it, just not sjc1 vpn
Marking invalid since it is both an uncommon dir to need to get at outside of the automated machines, and because I can fix it locally by using the new VPN, which I should already have switched to.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•