Closed Bug 642715 Opened 13 years ago Closed 10 years ago

make script factory errors more discoverable

Categories

(Release Engineering :: General, defect, P5)

Product:
Release Engineering
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 740142

People

(Reporter: jhford, Unassigned)

Details

(Whiteboard: [scripts]) 

During 4.0rc2 build 2, there was a repack with a random failure.  I ended up having to trace the code through to figure out what string to search for in the logs.

Lets have a standard string that is put in the log anywhere something bad happens.

something other than UNEXPECTED, FAIL, ERROR, etc would probably good to avoid namespace collisions.
just noticed bug 642700.  I think that while these bugs have the same root cause that they are different in objective.  One (642700) is to deal with the specific case, where this bug is to deal with the general case of "something broke, what?"
(In reply to comment #1)
> just noticed bug 642700.  I think that while these bugs have the same root
> cause that they are different in objective.  One (642700) is to deal with the
> specific case, where this bug is to deal with the general case of "something
> broke, what?"

I think it's pretty hard for script factory to do anything about it. if these scripts were implemented in mozharness, then it would be easier!
OS: Mac OS X → All
Priority: -- → P5
Hardware: x86 → All
Whiteboard: [scripts]
Product: mozilla.org → Release Engineering
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.