Hi Nilesh,
Nilesh Patra, on 2023-01-16:
> https://github.com/gem-pasteur/macsyfinder/issues/58
>
> I've now added a comment saying that the patch fixes these random
> issues. I am tempted to merge this patch and upload, but I am not 100%
> confident if it is correct. And hence, a review would be
On Sun, Jan 15, 2023 at 04:36:39PM +0100, Santiago Vila wrote:
> El 15/1/23 a las 15:45, Nilesh Patra escribió:
> > On Sun, Jan 15, 2023 at 02:02:15PM +0100, Santiago Vila wrote:
> > > I can reproduce this build failure on Hetzner virtual machines with 2
> > > CPUs,
> > > where it fails randomly
El 15/1/23 a las 15:45, Nilesh Patra escribió:
On Sun, Jan 15, 2023 at 02:02:15PM +0100, Santiago Vila wrote:
I can reproduce this build failure on Hetzner virtual machines with 2 CPUs,
where it fails randomly 50% of the time.
Therefore, to reproduce the randomness, you have to try many times.
Control: tags -1 - moreinfo
Control: tags -1 + confirmed
Control: severity -1 important
Hi Santiago,
Santiago Vila, on 2023-01-15:
> I can reproduce this build failure on Hetzner virtual machines with 2 CPUs,
> where it fails randomly 50% of the time.
Thank you for the additional information, I
Hi,
On 15/01/23 at 20:15 +0530, Nilesh Patra wrote:
> On Sun, Jan 15, 2023 at 02:02:15PM +0100, Santiago Vila wrote:
> > I can reproduce this build failure on Hetzner virtual machines with 2 CPUs,
> > where it fails randomly 50% of the time.
> >
> > Therefore, to reproduce the randomness, you
On Sun, Jan 15, 2023 at 02:02:15PM +0100, Santiago Vila wrote:
> I can reproduce this build failure on Hetzner virtual machines with 2 CPUs,
> where it fails randomly 50% of the time.
>
> Therefore, to reproduce the randomness, you have to try many times.
I built it 50 times on
Hi.
I can reproduce this build failure on Hetzner virtual machines with 2 CPUs,
where it fails randomly 50% of the time.
Therefore, to reproduce the randomness, you have to try many times.
(On Hetzner virtual machines with only one CPU, it does not seem to fail).
Thanks.
On 15/01/23 at 15:58 +0530, Nilesh Patra wrote:
> On Sun, Jan 15, 2023 at 10:08:18AM +0100, Lucas Nussbaum wrote:
> > On 15/01/23 at 12:20 +0530, Nilesh Patra wrote:
> > > It passes for me in a clean unstable chroot. Could you please check if
> > > this
> > > is still persistent or was just a
On Sun, Jan 15, 2023 at 10:08:18AM +0100, Lucas Nussbaum wrote:
> On 15/01/23 at 12:20 +0530, Nilesh Patra wrote:
> > It passes for me in a clean unstable chroot. Could you please check if this
> > is still persistent or was just a on-off thing?
>
> I can still reproduce
I tried building it in a
Hi Nilesh
On 15/01/23 at 12:20 +0530, Nilesh Patra wrote:
> It passes for me in a clean unstable chroot. Could you please check if this
> is still persistent or was just a on-off thing?
I can still reproduce
Lucas
Hi Lucas,
On Sat, 14 Jan 2023 13:41:14 +0100 Lucas Nussbaum wrote:
Source: macsyfinder
Version: 2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240:
Source: macsyfinder
Version: 2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules
12 matches
Mail list logo
