On 2023-03-21 13:17, Brian Inglis wrote:
On 2023-01-19 12:31, Brian Inglis via Cygwin wrote:
On 2023-01-19 11:38, Corinna Vinschen via Cygwin wrote:
On Jan 19 09:31, Brian Inglis via Cygwin wrote:
On 2023-01-18 02:42, Corinna Vinschen via Cygwin wrote:
I tested this yesterday with 7 runs on
On 2023-01-19 11:38, Corinna Vinschen via Cygwin wrote:
On Jan 19 09:31, Brian Inglis via Cygwin wrote:
On 2023-01-18 02:42, Corinna Vinschen via Cygwin wrote:
I tested this yesterday with 7 runs on two machines in parallel while
building Cygwin continuously in another Window, and cygcheck
Corinna Vinschen, on January 19, 2023 1:39 PM wrote:
>...(had to skip 3.4.4, don't ask...)
LOL.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info:
On Jan 19 09:31, Brian Inglis via Cygwin wrote:
> On 2023-01-18 02:42, Corinna Vinschen via Cygwin wrote:
> > I tested this yesterday with 7 runs on two machines in parallel while
> > building Cygwin continuously in another Window, and cygcheck still with
> > high-entropy-VA enabled. And one of
On 2023-01-19 09:31, Brian Inglis via Cygwin wrote:
On 2023-01-18 02:42, Corinna Vinschen via Cygwin wrote:
On Jan 18 18:16, Takashi Yano via Cygwin wrote:
On Jan 16 22:42, Corinna Vinschen via Cygwin wrote:
I pushed some patches to fix this issue. Excessive debugging indicated
that the
On 2023-01-18 02:42, Corinna Vinschen via Cygwin wrote:
Hi Takashi,
On Jan 18 18:16, Takashi Yano via Cygwin wrote:
On Jan 16 22:42, Corinna Vinschen via Cygwin wrote:
I pushed some patches to fix this issue. Excessive debugging indicated
that the reason cygcheck fails in this way is:
- It's
Hi Takashi,
On Jan 18 18:16, Takashi Yano via Cygwin wrote:
> > On Jan 16 22:42, Corinna Vinschen via Cygwin wrote:
> > I pushed some patches to fix this issue. Excessive debugging indicated
> > that the reason cygcheck fails in this way is:
> >
> > - It's a non-Cygwin process which
> >
> > -
On Tue, 17 Jan 2023 21:46:20 +0100
Corinna Vinschen wrote:
> Hi Takashi,
>
> On Jan 16 22:42, Corinna Vinschen via Cygwin wrote:
> > On Jan 16 16:18, Corinna Vinschen via Cygwin wrote:
> > > Actually, I' running your testcase on two machines in parallel now for
> > > quite some time, which only
Hi Takashi,
On Jan 16 22:42, Corinna Vinschen via Cygwin wrote:
> On Jan 16 16:18, Corinna Vinschen via Cygwin wrote:
> > Actually, I' running your testcase on two machines in parallel now for
> > quite some time, which only one hunk of 60675f1a7eb2 reverted, i.e.
> >
> > diff --git
Hi Takashi,
On Jan 16 16:18, Corinna Vinschen via Cygwin wrote:
> Actually, I' running your testcase on two machines in parallel now for
> quite some time, which only one hunk of 60675f1a7eb2 reverted, i.e.
>
> diff --git a/winsup/cygwin/mm/shared.cc b/winsup/cygwin/mm/shared.cc
> index
On 2023-01-16 08:18, Corinna Vinschen via Cygwin wrote:
Hi Takashi,
On Jan 16 23:45, Takashi Yano via Cygwin wrote:
On Mon, 16 Jan 2023 11:23:54 +0100
Corinna Vinschen wrote:
On Jan 16 18:02, Takashi Yano via Cygwin wrote:
[...]
Errors seem to be three types: (null), cygpid.xxx and shared.5.
On 2023-01-16 08:40, Jon Turney via Cygwin wrote:
On 10/01/2023 00:00, Brian Inglis via Cygwin wrote:
On Mon, 9 Jan 2023 14:36:44 +0100, Corinna Vinschen wrote:> On Dec 29
21:59, Brian Inglis via Cygwin wrote:
I got some hangs (deadlock?) between (parallel?) make jobs, top,
procps, and even ls
On 10/01/2023 00:00, Brian Inglis via Cygwin wrote:
On Mon, 9 Jan 2023 14:36:44 +0100, Corinna Vinschen wrote:> On Dec 29
21:59, Brian Inglis via Cygwin wrote:
I got some hangs (deadlock?) between (parallel?) make jobs, top,
procps, and
even ls /proc/*/ when trying to cygport all check curl or
Hi Takashi,
On Jan 16 23:45, Takashi Yano via Cygwin wrote:
> On Mon, 16 Jan 2023 11:23:54 +0100
> Corinna Vinschen wrote:
> > On Jan 16 18:02, Takashi Yano via Cygwin wrote:
> > [...]
> > > Errors seem to be three types: (null), cygpid.xxx and shared.5.
> > > I'm not sure what is happening and
On Mon, 16 Jan 2023 11:23:54 +0100
Corinna Vinschen wrote:
> On Jan 16 18:02, Takashi Yano via Cygwin wrote:
> > Hi Corinna,
> >
> > On Mon, 9 Jan 2023 14:20:56 +0100
> > Corinna Vinschen wrote:
> > > On Jan 2 17:21, Takashi Yano via Cygwin wrote:
> > > > On Mon, 2 Jan 2023 14:38:03 +0900
> > >
On Jan 16 18:02, Takashi Yano via Cygwin wrote:
> Hi Corinna,
>
> On Mon, 9 Jan 2023 14:20:56 +0100
> Corinna Vinschen wrote:
> > On Jan 2 17:21, Takashi Yano via Cygwin wrote:
> > > On Mon, 2 Jan 2023 14:38:03 +0900
> > > Takashi Yano wrote:
> > > > On Mon, 2 Jan 2023 11:32:01 +0900
> > > >
Hi Corinna,
On Mon, 9 Jan 2023 14:20:56 +0100
Corinna Vinschen wrote:
> On Jan 2 17:21, Takashi Yano via Cygwin wrote:
> > On Mon, 2 Jan 2023 14:38:03 +0900
> > Takashi Yano wrote:
> > > On Mon, 2 Jan 2023 11:32:01 +0900
> > > Takashi Yano wrote:
> > > > On Sat, 31 Dec 2022 13:01:29 -0700
> > >
On Jan 10 19:01, Takashi Yano via Cygwin wrote:
> On Mon, 9 Jan 2023 18:13:26 +0100
> Corinna Vinschen wrote:
> > If q->sigtls is NULL, the signal is nevertheless waiting for being
> > handled. It's just not directed at a specific thread. Beats me, why
> > this didn't occur in my testing. The
On Mon, 9 Jan 2023 18:13:26 +0100
Corinna Vinschen wrote:
> If q->sigtls is NULL, the signal is nevertheless waiting for being
> handled. It's just not directed at a specific thread. Beats me, why
> this didn't occur in my testing. The process signal info should contain
> the process-wide mask
On Mon, 9 Jan 2023 14:36:44 +0100, Corinna Vinschen wrote:> On Dec 29 21:59,
Brian Inglis via Cygwin wrote:
I got some hangs (deadlock?) between (parallel?) make jobs, top, procps, and
even ls /proc/*/ when trying to cygport all check curl or look at the
process statuses when builds hung under
On Jan 2 11:32, Takashi Yano via Cygwin wrote:
> On Thu, 29 Dec 2022 21:59:45 -0700
> Brian Inglis wrote:
> > I got some hangs (deadlock?) between (parallel?) make jobs, top, procps,
> > and
> > even ls /proc/*/ when trying to cygport all check curl or look at the
> > process
> > statuses
On Jan 3 08:03, Takashi Yano via Cygwin wrote:
> On Mon, 2 Jan 2023 11:32:01 +0900
> Takashi Yano wrote:
> > On Thu, 29 Dec 2022 21:59:45 -0700
> > Brian Inglis wrote:
> > > I got some hangs (deadlock?) between (parallel?) make jobs, top, procps,
> > > and
> > > even ls /proc/*/ when trying to
Hi Brian,
On Dec 29 21:59, Brian Inglis via Cygwin wrote:
> Hi folks,
>
> I got some hangs (deadlock?) between (parallel?) make jobs, top, procps, and
> even ls /proc/*/ when trying to cygport all check curl or look at the
> process statuses when builds hung under Cygwin 3.4.3 and 3.5.0-0.69...
On Jan 2 17:21, Takashi Yano via Cygwin wrote:
> On Mon, 2 Jan 2023 14:38:03 +0900
> Takashi Yano wrote:
> > On Mon, 2 Jan 2023 11:32:01 +0900
> > Takashi Yano wrote:
> > > On Sat, 31 Dec 2022 13:01:29 -0700
> > > Brian Inglis wrote:
> > > > was also getting the messages below locally and still
On Mon, 2 Jan 2023 11:32:01 +0900
Takashi Yano wrote:
> On Thu, 29 Dec 2022 21:59:45 -0700
> Brian Inglis wrote:
> > I got some hangs (deadlock?) between (parallel?) make jobs, top, procps,
> > and
> > even ls /proc/*/ when trying to cygport all check curl or look at the
> > process
> >
On Mon, 2 Jan 2023 14:38:03 +0900
Takashi Yano wrote:
> On Mon, 2 Jan 2023 11:32:01 +0900
> Takashi Yano wrote:
> > On Sat, 31 Dec 2022 13:01:29 -0700
> > Brian Inglis wrote:
> > > was also getting the messages below locally and still on GitHub scallywag:
> > >
> > > cygcheck (6936) child_copy:
On Mon, 2 Jan 2023 11:32:01 +0900
Takashi Yano wrote:
> On Sat, 31 Dec 2022 13:01:29 -0700
> Brian Inglis wrote:
> > was also getting the messages below locally and still on GitHub scallywag:
> >
> > cygcheck (6936) child_copy: cygheap read copy failed,
> >
> > ../curl/scallywag/1_x86_64
On Thu, 29 Dec 2022 21:59:45 -0700
Brian Inglis wrote:
> I got some hangs (deadlock?) between (parallel?) make jobs, top, procps, and
> even ls /proc/*/ when trying to cygport all check curl or look at the process
> statuses when builds hung under Cygwin 3.4.3 and 3.5.0-0.69...
>
> Had to
On Sat, 31 Dec 2022, Brian Inglis wrote:
> was also getting the messages below locally and still on GitHub scallywag:
>
> cygcheck (6936) child_copy: cygheap read copy failed,
>
> ../curl/scallywag/1_x86_64 build.log:2022-12-26T00:39:35.6163236Z 0
> [main] cygcheck (6936) child_copy:
On 2022-12-29 21:59, Brian Inglis wrote:
I got some hangs (deadlock?) between (parallel?) make jobs, top, procps, and
even ls /proc/*/ when trying to cygport all check curl or look at the process
statuses when builds hung under Cygwin 3.4.3 and 3.5.0-0.69...
Had to revert to a Cygwin
Hi folks,
I got some hangs (deadlock?) between (parallel?) make jobs, top, procps, and
even ls /proc/*/ when trying to cygport all check curl or look at the process
statuses when builds hung under Cygwin 3.4.3 and 3.5.0-0.69...
Had to revert to a Cygwin 3.4.0-344 test build from Dec 16
31 matches
Mail list logo
