From: Neil Horman <nhorman@tuxdriver.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
john.mcnamara@intel.com, qian.q.xu@intel.com, ci@dpdk.org
Subject: Re: [dpdk-ci] [dpdk-dev] [PATCHv3 0/4] dpdk: enhance EXPERIMENTAL api tagging
Date: Tue, 9 Jan 2018 07:36:13 -0500 [thread overview]
Message-ID: <20180109123613.GA14094@hmswarspite.think-freely.org> (raw)
In-Reply-To: <4728124.4p1ub5D4TT@xps>
On Tue, Jan 09, 2018 at 10:20:05AM +0100, Thomas Monjalon wrote:
> 09/01/2018 02:32, Neil Horman:
> > On Fri, Jan 05, 2018 at 11:00:52AM -0500, Neil Horman wrote:
> > > On Fri, Jan 05, 2018 at 03:08:52PM +0100, Thomas Monjalon wrote:
> > > > 04/01/2018 13:56, Neil Horman:
> > > > > On Sat, Dec 30, 2017 at 12:15:17PM -0500, Neil Horman wrote:
> > > > > > Thomas-
> > > > > > I just noticed that the ci tests are failing on the intel compiler, which
> > > > > > makes very little sense to me, as the error is a permission error on a bash
> > > > > > script that added in this series, which works during the gcc compilation. Can
> > > > > > you take a look at that please?
> > > > > >
> > > > > > thanks
> > > > > > Neil
> > > > > >
> > > > > Ping again Thomas, I've still heard nothing from you or the CI group about
> > > > > getting more visibility into the odd permission problem in the CI runs this
> > > > > seems to be encountering. I'd love to fix it, but the information in the report
> > > > > is insufficient to have any idea whats going on and the problem does not occur
> > > > > on local builds. Please advise.
> > > >
> > > > Unfortunately, I have no clues about this setup.
> > > > The report is sent by sys_stv@intel.com.
> > > > Adding Qian as Cc.
> > > >
> > > > The error is "buildtools/experimentalsyms.sh: Permission denied"
> > > > And the file mode is 100755.
> > > >
> > > > Anyone from Intel to check what happens please?
> > > >
> > > Thank you Thomas. I would really like to get this pushed in, as others have
> > > acked it, but the lack of visibility into the CI errors is quite frustrating
> > > Neil
> > >
> > >
> > So I'm not sure where to go with this. I've emailed the ci group on their list,
> > I've asked them directly on this list, and asked you, Thomas for assistance in
> > getting hold of the ci maintainers, and there has been no response in over a
> > week now. This patch has been acked by a few people, and the builds work on
> > clang and gcc locally just fine. I'm inclined to ask you to take these patches
> > despite the ci errors. If the CI maintainers can't respond to needs for
> > visibility into the system, I don't think its reasonable to block patches based
> > on CI results.
> >
> > Thoughts?
> > Neil
>
> Yes, you're right, we can bypass this CI test.
>
Thank you, much appreciated.
Neil
next prev parent reply other threads:[~2018-01-09 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171201185628.16261-1-nhorman@tuxdriver.com>
[not found] ` <20171230171517.GA4393@neilslaptop.think-freely.org>
[not found] ` <20180104125631.GA919@hmswarspite.think-freely.org>
2018-01-05 14:08 ` Thomas Monjalon
2018-01-05 16:00 ` Neil Horman
2018-01-09 1:32 ` Neil Horman
2018-01-09 9:20 ` Thomas Monjalon
2018-01-09 12:36 ` Neil Horman [this message]
2018-01-19 15:44 ` Neil Horman
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=20180109123613.GA14094@hmswarspite.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=qian.q.xu@intel.com \
--cc=thomas@monjalon.net \
/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).