Skip to content
  1. Apr 21, 2015
  2. Apr 20, 2015
  3. Apr 17, 2015
  4. Apr 16, 2015
  5. Apr 15, 2015
  6. Apr 14, 2015
  7. Apr 13, 2015
    • Felix Belzunce Arcos's avatar
      Tab major clean up · 6528ff1e
      Felix Belzunce Arcos authored
      6528ff1e
    • Felix Belzunce Arcos's avatar
      Corrent tab in assertTrue again · dab56506
      Felix Belzunce Arcos authored
      dab56506
    • Felix Belzunce Arcos's avatar
      Corrent tab in assertTrue · e5e53be0
      Felix Belzunce Arcos authored
      e5e53be0
    • Felix Belzunce Arcos's avatar
      Correct tests · 9afb092b
      Felix Belzunce Arcos authored
      9afb092b
    • Harald Albers's avatar
      Remove empty list item from changelog · ebffeccd
      Harald Albers authored
      ebffeccd
    • Harald Albers's avatar
      Remove extra 1.609 sections from changelog · 7887dc2d
      Harald Albers authored
      7887dc2d
    • Stephen Connolly's avatar
      [FIXED JENKINS-27708][FIXED JENKINS-27871] Ensure that identification of... · 5880ed83
      Stephen Connolly authored
      [FIXED JENKINS-27708][FIXED JENKINS-27871]  Ensure that identification of blocked tasks is using the live state.
      
      - The creation of a snapshot itself should be relatively cheap given the expected rate of
        job execution. You probably would need 100's of jobs starting execution every iteration
        of maintain() before this could even start to become an issue and likely the calculation
        of isBuildBlocked(p) will become a bottleneck before updateSnapshot() will. Additionally
        since the snapshot itself only ever has at most one reference originating outside of the stack
        it should remain in the eden space and thus be cheap to GC.
      
      - JENKINS-27708 comments 225819 and 225906 provide more complex but logically equivalent fixes of
        this issue. I am favouring this approach as it is simpler and provides less scope for error as any
        new helper methods can just rely on the snapshot being up to date whereas with the other
        two candidates if a new helper method is introduced there is the potential to miss adding support
        for the live view. The comment 225819 has the risk of introducing extra lock contention while
        the comment 225906 version forces every access to the helper methods to pass a second memory
        barrier
      5880ed83
Loading