Skip to content

GitLab

MAJ terminée. Nous sommes passés en version 14.0.12 . Pour consulter les release notes associée c'est ici :
https://about.gitlab.com/releases/2021/06/22/gitlab-14-0-released/
https://about.gitlab.com/releases/2021/06/24/gitlab-14-0-1-released/
https://about.gitlab.com/releases/2021/07/06/gitlab-14-0-3-released/
https://about.gitlab.com/releases/2021/07/07/critical-security-release-gitlab-14-0-4-released/
https://about.gitlab.com/releases/2021/07/08/gitlab-14-0-5-released/
https://about.gitlab.com/releases/2021/07/20/gitlab-14-0-6-released/
https://about.gitlab.com/releases/2021/08/03/security-release-gitlab-14-1-2-released/
https://about.gitlab.com/releases/2021/08/26/gitlab-14-0-8-released/
https://about.gitlab.com/releases/2021/08/31/security-release-gitlab-14-2-2-released/
https://about.gitlab.com/releases/2021/09/02/gitlab-14-0-10-released/
https://about.gitlab.com/releases/2021/09/27/gitlab-14-0-11-released/
https://about.gitlab.com/releases/2021/11/05/gitlab-14-0-12-released/

Switch branch/tag
  1. 08 Apr, 2015 6 commits
  3. 07 Apr, 2015 2 commits
  5. 05 Apr, 2015 2 commits
  7. 03 Apr, 2015 2 commits
  9. 02 Apr, 2015 6 commits
  11. 01 Apr, 2015 1 commit
  13. 31 Mar, 2015 1 commit
  15. 28 Mar, 2015 2 commits
  17. 27 Mar, 2015 1 commit
    • Guillaume Melquiond's avatar
      Improve why3-cpulimit so that it forcibly kills processes after a while. · 21198e50
      Guillaume Melquiond authored 
      A child process (e.g. CVC4) might catch SIGXCPU. If it gets stuck then, it
won't consume any additional cpu time, so the system won't forcibly kill
it. So why3-cpulimit has to kill it.

Note that, if the system is overloaded, why3-cpulimit might kill the child
process before it has even reached its cpu time limit. Hopefully, the 60'
additional time will suffice in practice.
      21198e50
  19. 26 Mar, 2015 1 commit
  21. 25 Mar, 2015 7 commits
  23. 24 Mar, 2015 3 commits
  25. 23 Mar, 2015 3 commits
  27. 22 Mar, 2015 3 commits