All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1362] Framework cleanup before extraction fails due to root files
Date: Wed, 10 Jan 2024 12:19:40 +0000	[thread overview]
Message-ID: <bug-1362-3@http.bugs.dpdk.org/> (raw)

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

https://bugs.dpdk.org/show_bug.cgi?id=1362

            Bug ID: 1362
           Summary: Framework cleanup before extraction fails due to root
                    files
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: dts
          Assignee: dev@dpdk.org
          Reporter: juraj.linkes@pantheon.tech
                CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
  Target Milestone: ---

233201 2023/07/18 13:16:49 - SUT 1 - INFO - Copying DPDK tarball to SUT.
233202 2023/07/18 13:16:49 - SUT 1 - INFO - Extracting DPDK tarball on SUT:
'/tmp/dpdk.tar.xz' into '/tmp/dpdk-22.07'.
233203 2023/07/18 13:16:49 - SUT 1 - INFO - Sending: 'rm -rf /tmp/dpdk-22.07'
233204 2023/07/18 13:16:50 - SUT 1 - DEBUG - Received from 'rm -rf
/tmp/dpdk-22.07':
233205 stdout: ''
233206 stderr: 'rm: cannot remove
'/tmp/dpdk-22.07/x86_64-linux-native-gcc/app/test/trace_autot-2023-07-18-AM-08-45-39':
Permission denied


It's possible that the previously extracted tarball was done with admin
privileges. It's also possible that it was created outside DTS.

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

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

                 reply	other threads:[~2024-01-10 12:19 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-1362-3@http.bugs.dpdk.org/ \
    --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.