| 
    
      
  | 
  
 Chromium Code Reviews| 
         Created: 
          4 years, 3 months ago by kjellander_webrtc Modified: 
          4 years, 3 months ago Reviewers: 
          
          phoglund, anatolid CC: 
          
          
          
          webrtc-reviews_webrtc.org, qiang.lu, niklas.enbom, yujie_mao (webrtc), peah-webrtc Target Ref: 
          
          
          refs/pending/heads/master Project: 
          
          webrtc Visibility: 
          
          
          
        Public.  | 
      
        
  DescriptionPRESUBMIT: Make BUG= field mandatory.
Also show a descriptive error message if BUG= field is missing.
BUG=webrtc:6326
NOTRY=True
TESTED=Verified the presubmit error using this very same CL (but with BUG= left empty).
Committed: https://crrev.com/d1e26a9bc14614a708bc71d9ba52ce191e406486
Cr-Commit-Position: refs/heads/master@{#14291}
   
  Patch Set 1 #
 Messages
    Total messages: 20 (9 generated)
     
  
  
 Description was changed from ========== PRESUBMIT: Make BUG= field mandatory. Also show a descriptive error message if BUG= field is missing. BUG= ========== to ========== PRESUBMIT: Make BUG= field mandatory. Also show a descriptive error message if BUG= field is missing. BUG=webrtc:6326 TESTED=Verified the presubmit error using this very same CL (but with BUG= left empty). ========== 
 kjellander@webrtc.org changed reviewers: + phoglund@webrtc.org 
 Patchset #1 (id:1) has been deleted 
 Patchset #1 (id:20001) has been deleted 
 As discussed with Anatoli and Chris, see referenced bug for more info. 
 Arguably we should have some way of bypassing this (BUG=None), but maybe that was the old behavior? I think bypasses are nice in many situations, but then we need to build a culture that it should only be used in special circumstances and under responsibility (like TBRs etc). Isn't a presubmit warning enough here? 
 On 2016/09/08 07:45:01, phoglund wrote: > Arguably we should have some way of bypassing this (BUG=None), but maybe that > was the old behavior? I think bypasses are nice in many situations, but then we > need to build a culture that it should only be used in special circumstances and > under responsibility (like TBRs etc). Isn't a presubmit warning enough here? Right, BUG=None is bypassing this check easily, but BUG= is the default from the template, and only displays a warning (that nobody reads) and the presubmit trybot happily submits the CL. Talk to Anatoli and Chris to see how many CLs are missing bug references - they're a lot. 
 On 2016/09/08 08:01:00, kjellander_webrtc wrote: > On 2016/09/08 07:45:01, phoglund wrote: > > Arguably we should have some way of bypassing this (BUG=None), but maybe that > > was the old behavior? I think bypasses are nice in many situations, but then > we > > need to build a culture that it should only be used in special circumstances > and > > under responsibility (like TBRs etc). Isn't a presubmit warning enough here? > > Right, BUG=None is bypassing this check easily, but BUG= is the default from the > template, and only displays a warning (that nobody reads) and the presubmit > trybot happily submits the CL. > Talk to Anatoli and Chris to see how many CLs are missing bug references - > they're a lot. Ok, so this change forces you to type something in the bug field, but None is acceptable? 
 On 2016/09/08 08:42:46, phoglund wrote: > On 2016/09/08 08:01:00, kjellander_webrtc wrote: > > On 2016/09/08 07:45:01, phoglund wrote: > > > Arguably we should have some way of bypassing this (BUG=None), but maybe > that > > > was the old behavior? I think bypasses are nice in many situations, but then > > we > > > need to build a culture that it should only be used in special circumstances > > and > > > under responsibility (like TBRs etc). Isn't a presubmit warning enough here? > > > > Right, BUG=None is bypassing this check easily, but BUG= is the default from > the > > template, and only displays a warning (that nobody reads) and the presubmit > > trybot happily submits the CL. > > Talk to Anatoli and Chris to see how many CLs are missing bug references - > > they're a lot. > > Ok, so this change forces you to type something in the bug field, but None is > acceptable? Yeah, this change essentially just changes the informative message into a blocking Error for the presubmit. The informative message triggered too if you left it out of just had it empty, but I figure nobody reads those. None will make it go away, yes. 
 On 2016/09/08 09:04:43, kjellander_webrtc wrote: > On 2016/09/08 08:42:46, phoglund wrote: > > On 2016/09/08 08:01:00, kjellander_webrtc wrote: > > > On 2016/09/08 07:45:01, phoglund wrote: > > > > Arguably we should have some way of bypassing this (BUG=None), but maybe > > that > > > > was the old behavior? I think bypasses are nice in many situations, but > then > > > we > > > > need to build a culture that it should only be used in special > circumstances > > > and > > > > under responsibility (like TBRs etc). Isn't a presubmit warning enough > here? > > > > > > Right, BUG=None is bypassing this check easily, but BUG= is the default from > > the > > > template, and only displays a warning (that nobody reads) and the presubmit > > > trybot happily submits the CL. > > > Talk to Anatoli and Chris to see how many CLs are missing bug references - > > > they're a lot. > > > > Ok, so this change forces you to type something in the bug field, but None is > > acceptable? > > Yeah, this change essentially just changes the informative message into a > blocking Error for the presubmit. > The informative message triggered too if you left it out of just had it empty, > but I figure nobody reads those. > > None will make it go away, yes. ok, lgtm 
 kjellander@webrtc.org changed reviewers: + anatolid@webrtc.org 
 anatolid@: should we submit this now or wait? 
 Description was changed from ========== PRESUBMIT: Make BUG= field mandatory. Also show a descriptive error message if BUG= field is missing. BUG=webrtc:6326 TESTED=Verified the presubmit error using this very same CL (but with BUG= left empty). ========== to ========== PRESUBMIT: Make BUG= field mandatory. Also show a descriptive error message if BUG= field is missing. BUG=webrtc:6326 NOTRY=True TESTED=Verified the presubmit error using this very same CL (but with BUG= left empty). ========== 
 On 2016/09/08 10:07:27, kjellander_webrtc wrote: > anatolid@: should we submit this now or wait? Submitting now. 
 The CQ bit was checked by kjellander@webrtc.org 
 CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/... 
 
            
              
                Message was sent while issue was closed.
              
            
             
          
        Description was changed from ========== PRESUBMIT: Make BUG= field mandatory. Also show a descriptive error message if BUG= field is missing. BUG=webrtc:6326 NOTRY=True TESTED=Verified the presubmit error using this very same CL (but with BUG= left empty). ========== to ========== PRESUBMIT: Make BUG= field mandatory. Also show a descriptive error message if BUG= field is missing. BUG=webrtc:6326 NOTRY=True TESTED=Verified the presubmit error using this very same CL (but with BUG= left empty). ========== 
 
            
              
                Message was sent while issue was closed.
              
            
             
          
        Committed patchset #1 (id:40001) 
 
            
              
                Message was sent while issue was closed.
              
            
             
          
        Description was changed from ========== PRESUBMIT: Make BUG= field mandatory. Also show a descriptive error message if BUG= field is missing. BUG=webrtc:6326 NOTRY=True TESTED=Verified the presubmit error using this very same CL (but with BUG= left empty). ========== to ========== PRESUBMIT: Make BUG= field mandatory. Also show a descriptive error message if BUG= field is missing. BUG=webrtc:6326 NOTRY=True TESTED=Verified the presubmit error using this very same CL (but with BUG= left empty). Committed: https://crrev.com/d1e26a9bc14614a708bc71d9ba52ce191e406486 Cr-Commit-Position: refs/heads/master@{#14291} ========== 
 
            
              
                Message was sent while issue was closed.
              
            
             
          
        Patchset 1 (id:??) landed as https://crrev.com/d1e26a9bc14614a708bc71d9ba52ce191e406486 Cr-Commit-Position: refs/heads/master@{#14291}  | 
    ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
