On 10/9/20 5:40 PM, Felix Lechner wrote:
> Perhaps it was an error to mix sysread [1] with print (as noted in the
> documentation, even though the handles are different). Can you try
> syswrite [2] in the three lines here [3] instead of print, please?
Already tried it in one of my tests, doesn't
Hi Baptiste,
On Fri, Oct 9, 2020 at 6:41 AM Baptiste Beauplat wrote:
>
> The problem seems to be an interaction between the pipes, the process,
> perl and the kernel.
Perhaps it was an error to mix sysread [1] with print (as noted in the
documentation, even though the handles are different).
Hi Felix,
I did a couple more testing and here are the results:
- Using the bpo kernel solves the issue
- Using a smaller write on the read buffer solves the issue (tested with 4k)
What does not solve the issue, that I've tried:
- Writing only when the pipes are available for writing (using
Hi Baptiste,
On Fri, Oct 9, 2020 at 2:03 AM Felix Lechner wrote:
>
> Untarring is an expensive operation, and the two indices would
> otherwise require two such operations in addition to the actual
> unpacking.
Upon re-reading, my wording was perhaps a bit unclear. Here, 'index'
refers to 'tar
On 10/9/20 11:03 AM, Felix Lechner wrote:
> Hi Baptiste,
>
> On Fri, Oct 9, 2020 at 12:30 AM Baptiste BEAUPLAT wrote:
>>
>> the issue is intermittent
>
> In which percentage of cases does this issue occur, please?
With xargs I'd say 90% reproducibility.
Single run is closer to 1 out of 3.
> I
Hi Baptiste,
On Fri, Oct 9, 2020 at 12:30 AM Baptiste BEAUPLAT wrote:
>
> the issue is intermittent
In which percentage of cases does this issue occur, please?
I am unable to reproduce it in twenty runs locally on stable-bpo, in
which I develop ("bare metal"), without the 'time' command which
On 10/9/20 9:50 AM, Felix Lechner wrote:
> Hi Baptiste,
>
> On Fri, Oct 9, 2020 at 12:30 AM Baptiste BEAUPLAT wrote:
>>
>> seq 1 2 | time xargs -I {} -P 0 lintian -d
>> gnome-user-docs_3.38.1-1_amd64.changes
>
> What is the purpose of the 'seq' in this command, please?
To produce **two**
Hi Baptiste,
On Fri, Oct 9, 2020 at 12:30 AM Baptiste BEAUPLAT wrote:
>
> seq 1 2 | time xargs -I {} -P 0 lintian -d
> gnome-user-docs_3.38.1-1_amd64.changes
What is the purpose of the 'seq' in this command, please?
> The issue is only reproducible when the following criteria are meet:
>
Package: lintian
Version: 2.97.0~bpo10+1
Severity: important
Dear maintainer,
On mentors.debian.net, our worker got stuck twice while running lintian
on two separate packages. While I haven't been able to reproduce the
issue with the first package, the second did it.
# The issue
Lintian hangs
9 matches
Mail list logo
