From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1383] DTS: clean up old tarball before copying a new one over
Date: Wed, 21 Feb 2024 15:46:52 +0000 [thread overview]
Message-ID: <bug-1383-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1383
Bug ID: 1383
Summary: DTS: clean up old tarball before copying a new one
over
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: jspewock@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
Currently we just scp over a tarball from the tester to the SUT as part of a
build target setup without checking to see if one exists. This works if you
always run DTS as the same user, but if multiple different users run DTS
back-to-back the second user will get a failure when trying to copy over the
tarball because scp cannot write over the existing one which the running user
does not own.
This is very easy to fix by simply logging onto the SUT and deleting the
tarball that is already in /tmp, but considering we write DTS under the
expectation that people could run as non-root users, it seems like it could be
worth making a simple quality of life change to make this easier.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3272 bytes --]
next reply other threads:[~2024-02-21 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 15:46 bugzilla [this message]
2024-03-19 18:53 ` [DPDK/DTS Bug 1383] DTS: clean up old tarball before copying a new one over bugzilla
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-1383-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.