DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: Cody Cheng <ccheng@iol.unh.edu>,
	ci@dpdk.org,  David Marchand <david.marchand@redhat.com>
Subject: What important system information is missing from unit/compile test reports?
Date: Fri, 11 Oct 2024 10:57:32 -0400	[thread overview]
Message-ID: <CAJvnSUB=cx9Xsfz_GUA7Q4vcZ98yGfJz0ysAw8Arj1kVE6fZPQ@mail.gmail.com> (raw)

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

When the Community Lab sends a test report email for a unit/compile test,
it provides a footer section with basic system info, for each system which
ran a test. They look like:

FreeBSD 14.1
    Kernel: 14.1-RELEASE-p3
    Compiler: clang 18.1.5

example:
https://inbox.dpdk.org/test-report/6708ccf8.050a0220.3a6b20.6f12SMTPIN_ADDED_MISSING@mx.google.com/T/#u

Should anything be added to this short list? CPU Model? Anything else?

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

                 reply	other threads:[~2024-10-11 14:58 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='CAJvnSUB=cx9Xsfz_GUA7Q4vcZ98yGfJz0ysAw8Arj1kVE6fZPQ@mail.gmail.com' \
    --to=probb@iol.unh.edu \
    --cc=ccheng@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    /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).