From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>,
"'Haritha D'" <Harithamma.D@ibm.com>
Cc: <git@vger.kernel.org>, "'Kristoffer Haugsbakk'" <code@khaugsbakk.name>
Subject: RE: [PATCH v3] build: support z/OS (OS/390).
Date: Fri, 1 Mar 2024 13:25:03 -0500 [thread overview]
Message-ID: <04df01da6c05$caaa5dd0$5fff1970$@nexbridge.com> (raw)
In-Reply-To: <xmqqbk7x6cox.fsf@gitster.g>
On Friday, March 1, 2024 1:15 PM, Junio C Hamano wrote:
>Haritha D <Harithamma.D@ibm.com> writes:
>
>> The win test(7) test case failed stating the reason as "The Operation
>> cancelled". I saw that it failed after 5 hours 59 minutes of running
>> the test cases(build). How do I handle this?
>
>Those "win test (n)", at least some of them, seem to have been somewhat
flaky [*1*]. If you are certain you did not break them with
>your change, you do not have to fix them yourself.
>
>I am a wrong person to ask how the test failure that may [*2*] block GGG
submission can be circumvented, as I am not involved in that
>machinery at all.
>
>Thanks.
>
>
>[Footnotes]
>
>*1* Also I've seen osx-clang job time-out from time to time, without
> failing any specific test. Re-running failed jobs from the menu
> often make them pass, which is why I said "somewhat flaky".
>
>*2* I do not even know if GGG refuses to submit a series with a test
> failure, let alone if it allows to override such a safety if
> exists.
Which tests have been hanging on S390? We have occasional hangs on NonStop
that end up being attributed to our CI build system not supplying pipes
properly to git. It would be interesting if the same tests are having issues
on different platforms.
--Randall
next prev parent reply other threads:[~2024-03-01 18:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 14:21 [PATCH] This PR enables a successful git build on z/OS Haritha via GitGitGadget
2024-01-31 16:12 ` Kristoffer Haugsbakk
2024-01-31 17:58 ` Junio C Hamano
2024-01-31 17:12 ` Junio C Hamano
2024-02-23 3:48 ` [PATCH v2 0/2] " Haritha via GitGitGadget
2024-02-23 3:48 ` [PATCH v2 1/2] build: support z/OS (OS/390) Haritha D via GitGitGadget
2024-02-23 3:48 ` [PATCH v2 2/2] an improvement: removed configure.ac changes Haritha D via GitGitGadget
2024-02-23 7:38 ` Junio C Hamano
2024-02-23 7:37 ` [PATCH v2 0/2] This PR enables a successful git build on z/OS Junio C Hamano
2024-02-25 6:10 ` [PATCH v3] build: support z/OS (OS/390) Haritha via GitGitGadget
2024-02-26 17:30 ` Junio C Hamano
2024-03-01 9:09 ` Haritha D
2024-03-01 14:39 ` Ghanshyam Thakkar
2024-03-01 18:15 ` Junio C Hamano
2024-03-01 18:25 ` rsbecker [this message]
2024-03-04 4:19 ` Haritha D
2024-03-06 5:44 ` [PATCH v4] " Haritha via GitGitGadget
2024-03-06 16:10 ` Junio C Hamano
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='04df01da6c05$caaa5dd0$5fff1970$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=Harithamma.D@ibm.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).