Closed Bug 992690 Opened 10 years ago Closed 10 years ago

Increase maxtime for browser-chrome-2. Again.

Categories

(Release Engineering :: General, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Assigned: philor)

References

Details

Attachments

(1 file)

[configs] 7200 seconds
1.08 KB, patch
armenzg
: review+
Details | Diff | Splinter Review 
So far, we've done 4200 -> 4800 -> 6000. Sometimes, we hit 6000 while we are just seconds away from done; more rarely, we hit it while we're still quite a way from done. This maxtime will get to shrink, or perhaps the whole idea of chunking browser-chrome will get to go away, when bug 984930 is done, so the value doesn't matter too much other than to tamp down my rage in the intervening time.

        Attachment #8402412 -
        Flags: review?(armenzg)

    
  

        Attachment #8402412 -
        Flags: review?(armenzg) → review+

    
    

    
  
in production

    
    

    
  
Thanks philor!
Blocks: 864866

    
  
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Component: General Automation → General

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






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: