From: Kevin Traynor <ktraynor@redhat.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: ci@dpdk.org, Lincoln Lavoie <lylavoie@iol.unh.edu>,
Aaron Conole <aconole@redhat.com>
Subject: Re: 21.11-staging branch
Date: Fri, 30 Aug 2024 13:20:01 +0100 [thread overview]
Message-ID: <8904f58c-667c-48d4-8219-c93eee067609@redhat.com> (raw)
In-Reply-To: <CAJvnSUDhKuxaT2vMimW7BdEC7YJ2ZDk9W-4Gb81d00yu67s3nQ@mail.gmail.com>
On 28/08/2024 20:56, Patrick Robb wrote:
> Hi Kevin,
>
Hi Patrick,
> I made some adjustments, did a manual trigger and the branch
> successfully cloned and checked out in 13 min, below our timeout. But,
> I am still a bit confused why this seems to pop up intermittently 1-2
> times per year... We are going to be making some upgrades to our
> Jenkins instance in the short term, maybe that will bring more
> stability to this CI pipeline.
>
The only clue is that I don't see any issues during a release cycle when
it's in use every few days etc. It seems to just happen after some
months of inactivity. So not critical, as long as you don't mind getting
an email about it 2 or 3 times a year ;-)
> Let me know the next time you push as I am interested to see if it's
> really "back to normal" or not.
>
I pushed this morning and it is working fine.
> sorry for the half answer here.
>
Thanks for your quick help as usual,
Kevin.
> Best,
> Patrick
>
> On Wed, Aug 28, 2024 at 3:31 PM Patrick Robb <probb@iol.unh.edu> wrote:
>>
>> Hi Kevin,
>>
>> Yes, I see it was another set of timeouts. Let me take a look. Sorry
>> about the inconvenience.
>>
>> On Wed, Aug 28, 2024 at 8:37 AM Kevin Traynor <ktraynor@redhat.com> wrote:
>>>
>>> Hi Patrick,
>>>
>>> I pushed to the 21.11-staging branch twice over the last few days but
>>> the ci didn't get reported as running [0].
>>>
>>> It's been a few months since it was used, so maybe we're hitting the
>>> timeout on clone again or something else.
>>>
>>> Would you be able to take a peek when you get a chance?
>>>
>>> thanks,
>>> Kevin.
>>>
>>> [0]
>>> https://dpdkdashboard.iol.unh.edu/results/dashboard/periodic_testing/?branch_id=16&page=0
>>>
>
prev parent reply other threads:[~2024-08-30 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 12:37 Kevin Traynor
2024-08-28 19:31 ` Patrick Robb
2024-08-28 19:56 ` Patrick Robb
2024-08-30 12:20 ` Kevin Traynor [this message]
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=8904f58c-667c-48d4-8219-c93eee067609@redhat.com \
--to=ktraynor@redhat.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=lylavoie@iol.unh.edu \
--cc=probb@iol.unh.edu \
/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).