If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Symbol server for tryserver appears to be down

RESOLVED WORKSFORME

Status

Release Engineering
General
--
major
RESOLVED WORKSFORME
6 years ago
4 years ago

People

(Reporter: khuey, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

Getting symbols from the symbol server for try builds does not appear to be working anymore.  When accessing http://build.mozilla.org/tryserver-symbols/ I get a 403 (as opposed to the expected 404).
The machine behind build.m.o changed in the downtime Wednesday morning, so please retest.

Updated

6 years ago
Depends on: 729667
(In reply to Nick Thomas [:nthomas] from comment #1)
> The machine behind build.m.o changed in the downtime Wednesday morning, so
> please retest.

I just tried now, and also get 403 (forbidden).
URLs like http://build.mozilla.org/tryserver-symbols/firefox-14.0a1-WINNT-20120420161534-symbols.txt are still working for me, both internally and externally, without auth.

The 403 is appropriate - indexes are disabled, so it's forbidden.  The directory exists, so 404 is not expected.

So.. I'm not sure what's wrong here.  Can you give more detail, or close as WORKSFORME?

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
Did we lose symbols for builds that are older than Wednesday?  Because I still can't load symbols for my build from Tuesday.
We should have 8 days worth of symbols, because that's the expiration policy and there was a periodic rsync from the old to new machines in place before the switch over.

For your push
  http://hg.mozilla.org/try/rev/b0a53b50259b
the manifest is at
  http://build.mozilla.org/tryserver-symbols/firefox-14.0a1-WINNT-20120423143035-symbols.txt
and requests like
  http://build.mozilla.org/tryserver-symbols/xul.pdb/6A9529CEA95442C1A0CB113BDCC565CB1/xul.sym
also load.

Could you give an example of a request which is failing ? Also, what IP do you get for build.mozilla.org ?
Created attachment 618842 [details]
Log
Created attachment 618843 [details]
Log
Attachment #618842 - Attachment is obsolete: true
We figured this out on IRC. The first request in the log is for
 http://build.mozilla.org/tryserver-symbols/AccessibleMarshal.pdb/AAA7080AC8984502B28E6F57FF237E411/AccessibleMarshal.pdb
which is actually the win32 debug build. We run 'make buildsymbols' for both opt and debug, but only do 'make uploadsymbols' for opt builds.

The question is, what should we do about that ?
I guess for try builds we should just upload symbols from the Windows debug builds. We don't do that for non-try builds because we don't want to have to keep them on the symbol server, but since the try symbol server is separate, it seems like less of an issue.
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.