Re: [External] Re: [PATCH v4 1/1] commit-graph.c: no lazy fetch in lookup_commit_in_graph()
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jul 12, 2022, 05:23 UTC
- Message-ID
- <xmqq1quqkiq2.fsf@gitster.g>
- In-Reply-To
- <CAKgqsWVD2108f0PyJGp6mVKp2cGd_V_MiiQO3SAPm+LEHcb2mA@mail.gmail.com>
Han Xin <hanxin.hx@bytedance.com> writes:
Show 10 quoted lines
>> I wonder if we can just run the test without any limit? If in an >> unattended CI situation, hopefully they will kick the job out due to >> quota, and on a developer workstation, there may be processes killed >> left and right, but that is only when the "infinite respawning" bug >> reappears. >> > > The tricky thing about using ulimit is that it's tied to the entire development > station. I have tried to run the test without any limit [1], it did finally be > canceled after 6 hours.
I am not worried so much about developer workstation, which people are sitting in front of. They can ^C any runaway test way before 6 hours just fine.
I am assuming that we do not have to be worried about CI settings too much, either, as they should already be prepared to catch run-away processes.