1. 29 Apr, 2016 1 commit
  2. 26 Feb, 2015 1 commit
  3. 25 Feb, 2015 2 commits
  4. 24 Feb, 2015 1 commit
    • machenbach's avatar
      Port chromium landmines script. · 89731cfb
      machenbach authored
      This runs the landmines script as a gclient hook. It can
      as such be used to clobber local checkouts when hooks are
      run locally.
      
      It is a softer version than chromium's landmines script, as
      it only deletes directories in the output directory due
      to compatibility with MSVS which has "build" hardcoded as
      output directory in several places.
      
      BUG=chromium:403263
      LOG=n
      
      Review URL: https://codereview.chromium.org/955463002
      
      Cr-Commit-Position: refs/heads/master@{#26831}
      89731cfb
  5. 09 Aug, 2014 1 commit
    • machenbach@chromium.org's avatar
      Fix v8 landmines script. · 7f156ffe
      machenbach@chromium.org authored
      Currently, some builders are in a clobber-landmine loop.
      
      Clobber deletes the .landmines tracker (sigh). Difficult to
      know if we are right after a clobber or if it is first-time
      landmines deployment. Also, a landmine-triggered clobber
      right after a clobber is not possible. Different clobber
      methods for msvs, xcode and make all have different
      blacklists of files that are not deleted.
      
      After the branch point, all v8 branch builders have to be
      manually clobbered, because the appearance of the
      landmines.py script and the first landmine request are in
      the same branch CL.
      
      TBR=jochen@chromium.org
      
      Review URL: https://codereview.chromium.org/457063002
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@23012 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      7f156ffe
  6. 08 Aug, 2014 1 commit
  7. 23 Jul, 2014 1 commit
    • machenbach@chromium.org's avatar
      Make landmines work on the first landmine. · 15398608
      machenbach@chromium.org authored
      With the original script, landmines don't work if the initial commit of the landmine script and the first landmine are in the same build. In this case, the landmine file wouldn't exist yet and no landmine would be triggered. But the updated landmine content would have still been written, omitting the landmine.
      
      Now, the script will initialize an empty landmine file if none exists. This will make sure that a landmine is set on the branch builders after the next branch point.
      
      This also adds some debugging output to better trace when landmines are set/deleted.
      
      BUG=
      R=jkummerow@chromium.org
      
      Review URL: https://codereview.chromium.org/410893002
      
      git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@22557 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      15398608
  8. 22 Jul, 2014 1 commit