1. 26 Sep, 2018 1 commit
  2. 23 Feb, 2018 1 commit
  3. 22 Feb, 2018 1 commit
  4. 13 Sep, 2017 2 commits
  5. 11 Sep, 2017 1 commit
  6. 22 Aug, 2017 1 commit
  7. 18 Mar, 2017 1 commit
  8. 16 Mar, 2017 9 commits
  9. 18 Oct, 2016 3 commits
  10. 12 Sep, 2016 1 commit
  11. 19 Aug, 2016 1 commit
  12. 16 Aug, 2016 1 commit
  13. 17 Jul, 2016 1 commit
    • Kamil Trzciński's avatar
      Solve very rare case resulting in dead-lock when cancelling a build · 7e6786eb
      Kamil Trzciński authored
      It's possible that we will block on Notify anonymous function, when the select loop a few lines below gets finished.
      It will happen, because we use unbuffered channel, but don't have a possibility to consume it.
      Thus this will block trace sending routing.
      Trace sending routine will not finish, thus it will block trace.Success/Fail resulting in ability to cleanup a executor and releasing a machine.
      
      This also renames BuildAbort to SystemInterrupt which is more accurate and makes a timeout a BuildError instead of SystemError.
      7e6786eb
  14. 14 Jul, 2016 1 commit
  15. 12 May, 2016 1 commit
  16. 04 May, 2016 1 commit
  17. 29 Apr, 2016 2 commits
  18. 30 Mar, 2016 1 commit
  19. 12 Mar, 2016 1 commit
  20. 29 Feb, 2016 1 commit
  21. 08 Feb, 2016 1 commit
  22. 06 Feb, 2016 2 commits
  23. 16 Jan, 2016 2 commits
  24. 25 Nov, 2015 1 commit