All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 45] Test compilation fails at 2nd iteration after running resource_autotest
Date: Thu, 10 May 2018 12:14:05 +0000	[thread overview]
Message-ID: <bug-45-3@http.dpdk.org/tracker/> (raw)

https://dpdk.org/tracker/show_bug.cgi?id=45

            Bug ID: 45
           Summary: Test compilation fails at 2nd iteration after running
                    resource_autotest
           Product: DPDK
           Version: 18.02
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: reshma.pattan@intel.com
  Target Milestone: ---

Test" compilation fails at second iteration after running sanity script test.
resource_autotest during test execution tries to open test_resource.c and if
found removes it.
Hence when we try to compile "test" in test folder again after running this
resource_autotest via sanity script, compilation fails as test_resource.c is
removed and not found.

DPDK version:
Latest dpdk-dpdk repo
OS:
Fedora 27, CentOS 7, FreeBSD
Compiler: gcc
Steps to reproduce
1. Compile dpdk-dpdk 
2. Compile "test" in test folder
3. Run Sanity Script or run resource_autotest UT
4. Re-compile "test" in test folder

Show the output from the previous commands.
dpdk-dpdk/test/test# make
make: *** No rule to make target 'test_resource.c', needed by
'test_resource.o'. Stop.

Expected Result
Compilation should be successful.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2018-05-10 12:14 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=bug-45-3@http.dpdk.org/tracker/ \
    --to=bugzilla@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.