From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 223] Using wrong/old commit id of the tree to apply the patch
Date: Tue, 19 Nov 2019 17:07:47 +0000 [thread overview]
Message-ID: <bug-223-149-UygmZ5m2Am@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-223-149@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=223
Jeremy Plsek (jplsek@iol.unh.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #2 from Jeremy Plsek (jplsek@iol.unh.edu) ---
Closing since this should have been resolved.
This is partially a separate issue, but some environments don't show commit
IDs, and that's because Jenkins sometimes runs the jobs in different workspaces
(Foo-Bar and Foo-Bar@2). Not sure how to resolve that. If this is important or
brought up again, a new ticket can be made.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2019-11-19 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 15:01 bugzilla
2019-11-19 17:07 ` bugzilla [this message]
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-223-149-UygmZ5m2Am@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=ci@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).