Closed Bug 598928 Opened 14 years ago Closed 9 years ago

Fix symbol cleanup for OpenSuSE symbols

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: ted, Assigned: wolfiR)

References

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2641] ) 

Currently the OpenSuSE symbols are being uploaded with index .txt files that don't match what our other builds upload:
xulrunner-1.9.2.9-3.1.i386-1110-symbols.txt

This means that our cleanup scripts are probably not going to work on these.

Wolfgang: can you either use our default index .txt files (even if we have to fix something to make them usable for you) or write your own cleanup script?

Our cleanup script is here:
http://hg.mozilla.org/build/tools/file/tip/buildfarm/breakpad/cleanup-breakpad-symbols.py
finally looking at it. It somehow got lost for me.
Status: NEW → ASSIGNED
Product: mozilla.org → Release Engineering
Found in triage. 

(In reply to Wolfgang Rosenauer [:wolfiR] from comment #1)
> finally looking at it. It somehow got lost for me.

wolfiR: Is this still an issue? If so, any progress?
Flags: needinfo?(mozilla)
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2634]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2634] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2641]
Is this still an issue? Seems like it's probably not....
Flags: needinfo?(mozilla) → needinfo?(ted)
QA Contact: mshal
It's not because I stopped uploading symbols as they are not recognized anymore correctly. RPMs own debuginfo creation somehow interferes. I wasn't able to solve this myself and it's currently not my priority.
We're going to decomission the NetApp symbol store soon anyway, so cleanup will be done on the symbols in S3.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(ted)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.