From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitlab-ci: disable realtime monitoring to unbreak Windows jobs
Date: Tue, 02 Sep 2025 09:35:09 -0700 [thread overview]
Message-ID: <xmqq8qiwlsn6.fsf@gitster.g> (raw)
In-Reply-To: <20250902-b4-pks-gitlab-ci-windows-defender-v1-1-fcb1f19321aa@pks.im> (Patrick Steinhardt's message of "Tue, 02 Sep 2025 12:47:41 +0200")
Patrick Steinhardt <ps@pks.im> writes:
> The GitLab CI runners using Windows machines have realtime monitoring
> via Windows Defender enabled by default. This has just now started to
> cause issues in our CI jobs using Microsoft Visual Studio:
>
> Program 'meson.exe' failed to run: Operation did not complete successfully because the file contains a virus or
> potentially unwanted softwareAt line:356 char:1
> + meson setup build --vsenv -Dperl=disabled -Dbackend_max_links=1 -Dcre ...
> + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.
> At line:356 char:1
> + meson setup build --vsenv -Dperl=disabled -Dbackend_max_links=1 -Dcre ...
> + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> + CategoryInfo : ResourceUnavailable: (:) [], ApplicationFailedException
> + FullyQualifiedErrorId : NativeCommandFailed
>
> The detected issue is more likely than not completely bogus, but it
> breaks the jobs.
>
> Fix the issue by disabling realtime monitoring. Besides unbreaking CI,
> it also improves our build times a bit:
>
> - Building Git goes from 26 to 22 minutes.
>
> - Executing tests goes from ~1h for one slice of tests to ~30 minutes.
Interesting observation. I didn't realize that we are shipping
virus or potentially unwanted software.
Does the same issue exist on other forges (like GitHub Actions), I
wonder?
next prev parent reply other threads:[~2025-09-02 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 10:47 [PATCH] gitlab-ci: disable realtime monitoring to unbreak Windows jobs Patrick Steinhardt
2025-09-02 16:35 ` Junio C Hamano [this message]
2025-09-03 4:39 ` Patrick Steinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq8qiwlsn6.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).