#26861: Bump available ulimit in runc container in tor-browser-build --------------------------------------------+------------------------------ Reporter: gk | Owner: tbb-team Type: defect | Status: needs_review Priority: Medium | Milestone: Component: Applications/Tor Browser | Version: Severity: Normal | Resolution: Keywords: tbb-rbm, TorBrowserTeam201807R | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: --------------------------------------------+------------------------------ Changes (by boklm):
* status: new => needs_review * keywords: tbb-rbm => tbb-rbm, TorBrowserTeam201807R Comment: I think we don't need to set any limit. The reason we had this limit set is that it is in the default example configuration. I am not sure however why other people were not affected by this issue. Maybe tjr's build machine has many cores, causing many gcc processes to be run in parallel and reaching the limit? There is a patch for removing the limit in branch `bug_26861`: https://gitweb.torproject.org/user/boklm/tor-browser- build.git/commit/?h=bug_26861&id=b7035b046a06b63edb2ca07e6e8d7afe3a5dc0bd -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26861#comment:1> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs