Control: notfound 1003530 2.114.0 Control: close 1003530 Hi Mattia, Thanks for the info. For the local test: I ran the test on my machine and it took slightly less than 1 hour to finish. I didn't know that recent lintian could take that much time for a full test. Looks like this is a duplicate of https://bugs.debian.org/993613 , so I am closing this bug report. Thanks, Boyuan Yang 在 2022-01-11星期二的 13:41 +0100，Mattia Rizzolo写道： > On Tue, Jan 11, 2022 at 07:29:32AM -0500, Boyuan Yang wrote: > > I just notice that lintian will never finish when checking some specific > > That's not correct. > > > https://mentors.debian.net/package/fcitx5-table-extra/ shows the lintian > > check > > result to be " lintian took too much time to run ". > > I actually never saw lintian *hang*. It just got quite slow. > > Specifically, on mentors.d.n we set a timeout for lintian of 30 minutes. > > We really don't want the whole site to spend hours processing an > incoming packages... > > > Notably, in mentors we don't use `-X cruft` to bypass the slowest > codepath in lintian, that can easily go over the 30 minutes time. > > > I am not 100% sure about the severity, but endless hang could be serious. > > Feel > > free to let me know if you have any questions. > > IMHO, this could just be merged with that other bug (that I'm not > looking up) about the cruft check being slow. > > > Did you try running lintian yourself to actually verify it hangs > somewhere?
Attachment:
signature.asc
Description: This is a digitally signed message part