Closed Bug 830874 Opened 11 years ago Closed 11 years ago

TBPL should no longer match against "Thread N (crashed)"

Categories

(Tree Management Graveyard :: TBPL, defect)

Product:
Tree Management Graveyard
Component:
TBPL
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

Attachments

(1 file)

Patch v1
1.80 KB, patch
philor
: review+
Details | Diff | Splinter Review 
Now that PROCESS-CRASH works across correctly across the board (cpp unit-tests and talos using mozcrash, mochitest and reftest using automationutils.py), we shouldn't ever get a "Thread N (crashed)" without also having a "PROCESS-CRASH".

Philor, your memory is much better than mine - am I overlooking anything?
Attached patch Patch v1 — — Splinter Review 

        Attachment #703274 -
        Flags: review?(philringnalda)

    
    

    
  
Comment on attachment 703274 [details] [diff] [review]
Patch v1

I think so, probably, I guess.

        Attachment #703274 -
        Flags: review?(philringnalda) → review+

    
  
Depends on: 833358

    
    

    
  
In production.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: