test suite reviews and discussions
 help / color / mirror / Atom feed
From: Jeremy Spewock <jspewock@iol.unh.edu>
To: dts@dpdk.org, ci@dpdk.org
Cc: Patrick Robb <probb@iol.unh.edu>, Lincoln Lavoie <lylavoie@iol.unh.edu>
Subject: DTS timeouts when compiling DPDK
Date: Tue, 16 Jan 2024 12:07:11 -0500	[thread overview]
Message-ID: <CAAA20UTs6QV92FGEHxSVpO7zzvaoeL35obfp0Xv-E3fzZBNsGA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1333 bytes --]

Hi all,

On the Community Lab test beds I have noticed something interesting about
the (old) DTS framework (NOTE: NOT the current dts framework rewrite
effort). We have begun seeing intermittent timeouts during the DTS
execution (specifically the DPDK compile command) on the DUT, almost
exclusively when doing 22.11 LTS testing, but also intermittently on main.

I'm not sure what the cause is, but most likely the timeout was set some
time ago and additions to DPDK and backporting to LTS releases has
gradually increased the compile time over time making the old timeout value
insufficient on some slower systems. For context, the current timeout for
compiling DPDK is set to be 30 minutes, but we have started to see builds
on some systems consistently require a few minutes more than that for the
compilation to complete. Does this sound reasonable to you all?

The compile timeout is not provided via config file, but is rather
hard-coded in /framework/dpdk_project.py. So, for now we have patched the
DTS we are running. I am willing to submit a patch to the DTS project
making this change, but I know the DTS project is without a maintainer
right now. Does anyone know whether (as discussed at the previous DPDK-CI
meeting) there will be a final round(s) of patches merged for the old DTS
project?

Thank you,
Jeremy Spewock

[-- Attachment #2: Type: text/html, Size: 1694 bytes --]

                 reply	other threads:[~2024-01-16 17:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAAA20UTs6QV92FGEHxSVpO7zzvaoeL35obfp0Xv-E3fzZBNsGA@mail.gmail.com \
    --to=jspewock@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dts@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).