Closed Bug 266176 Opened 20 years ago Closed 14 years ago

talkback fcsutil.pl considers a 302 status a reason to retry

Categories

(mozilla.org :: Talkback Server & Webtool, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: granrosebugs, Assigned: jay)

Details

Modified fcsutil.pl to retry once before failing when doing a newbuild. 
Successful runs return a status of 302 which fcsutil interprets as requiring a
retry, so each build is hitting the server twice when defining a new build:

/usr/bin/perl -I/builds/tinderbox/firefox-branch-l10n/Linux_2.4.20-28.8_Clobber/
mozilla/fullsoft/utils /builds/tinderbox/firefox-branch-l10n/Linux_2.4.20-28.8_C
lobber/mozilla/fullsoft/utils/fcsutil.pl -debug -newbuild -vendor MozillaOrg -pr
oduct Firefox10 -platform LinuxIntel -build 1 -server localhost:8080 2004102609
fcsutil.pl: version 1.5.105
fcsutil.pl: url: /admin/copyredir.cfm?ShouldSave=1&BuildID=2004102609&Deployment
ID=MozillaOrgFirefox10LinuxIntel1
fcsutil.pl: options: nofollow retry debug
fcsutil.pl: connecting to localhost:8080...
fcsutil.pl: sending request to localhost...
fcsutil.pl: waiting for data from localhost...
fcsutil.pl: header returns code 302 (Moved Temporarily)
fcsutil.pl: url: /admin/downloadmanifest.cfm?DeploymentID=MozillaOrgFirefox10Lin
uxIntel2004102609
fcsutil.pl: options: nofollow retry debug
fcsutil.pl: connecting to localhost:8080...
fcsutil.pl: sending request to localhost...
fcsutil.pl: waiting for data from localhost...
fcsutil.pl: header returns code 302 (Moved Temporarily)
Cc'ing Shiva so he can chime in with any thoughts.
Assignee: chase → nobody
Product: Firefox → Core
QA Contact: asa → build-config
Assignee: nobody → jay
Component: Build Config → Talkback Client
QA Contact: build-config → chofmann
Version: 1.0 Branch → 1.7 Branch
hmm, it seems fcsutil.pl is a server thing, not client. Correct me if I'm wrong.
Component: Talkback Client → Talkback Server & Webtool
Product: Core → mozilla.org
Version: 1.7 Branch → other
Talkback isn't used anymore:
R.Invalid now.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.