automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(106475-106476) sid(21351) job(DTS_AUTO_447) [V2, 2/2] doc/*: Add ASan test user guide
Date: 25 Jan 2022 01:01:06 -0800	[thread overview]
Message-ID: <722c05$fg6lkp@orsmga007-auth.jf.intel.com> (raw)

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

Test-Label: Intel-dts-doc-test
Test-Status: FAILURE
http://dpdk.org/patch/106476
Subject: [V2,2/2] doc/*: Add ASan test user guide

_Testing issues_

Diff:
	main.py
	framework/dts.py
	framework/asan_test.py
	conf/asan.cfg
	doc/dts_gsg/usr_guide/asan_test.rst

DPDK:
	commit 8a5a91401dc23ddab1ddea3667a17a615a25077f
	Author: Stephen Hemminger <stephen@networkplumber.org>
	Date:   Thu Dec 23 11:21:58 2021 -0800
	Comment: eal/linux: log hugepage create errors with filename

DTS:
	commit b057551331c95192b731d5bfbd48b86074d3bdac
	Author: Owen Hilyard <ohilyard@iol.unh.edu>
	Date:   Tue Jan 18 10:34:44 2022 -0500
	Comment: Fix hardcoded config folders

DOC test failed information:
dts_gsg


~~~~~~~~~~~~~
dts_gsg


~~~~~~~~~~~~~
dts_gsg


~~~~~~~~~~~~~~
dts_gsg


~~~~~~~~~~~~~~
dts_gsg


~~~~~~~~~~~~~~~~~~~~~~~
dts_gsg


~~~~~~~~~~~~~~~~~~~~~~~
dts_gsg


~~~~~~~~~~~~~~~~~~~~~~~~~
dts_gsg


~~~~~~~~~~~~~~~~~~~~~~~~~
dts_gsg


~~~~~~~~~~~~~~~~~~~~~~~~~~
dts_gsg


~~~~~~~~~~~~~~~~~~~~~~~~~~
looking for now-outdated files... none found
pickling environment... done
dts_gsg
done
preparing documents... done
writing output... [  8%] index
DPDK STV team

                 reply	other threads:[~2022-01-25  9:01 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='722c05$fg6lkp@orsmga007-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=dts-test-report@dpdk.org \
    --cc=test-report@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).