From: Gal Pressman <galpress@amazon.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
Benjamin Drung <benjamin.drung@cloud.ionos.com>,
<linux-rdma@vger.kernel.org>
Subject: Re: failed armel build of rdma-core 24.0-1
Date: Thu, 11 Jul 2019 11:00:44 +0300 [thread overview]
Message-ID: <bde8ef5c-10d4-0eae-efbf-5addff1633ff@amazon.com> (raw)
In-Reply-To: <20190711070744.GD23598@mtr-leonro.mtl.com>
On 11/07/2019 10:07, Leon Romanovsky wrote:
> On Thu, Jul 11, 2019 at 09:35:59AM +0300, Gal Pressman wrote:
>> On 10/07/2019 22:23, Jason Gunthorpe wrote:
>>> Benjamin,
>>>
>>> Can you confirm that something like this fixes these build problems?
>>>
>>> diff --git a/debian/rules b/debian/rules
>>> index 07c9c145ff090c..facb45170eacfc 100755
>>> --- a/debian/rules
>>> +++ b/debian/rules
>>> @@ -63,6 +63,7 @@ ifneq (,$(filter-out $(COHERENT_DMA_ARCHS),$(DEB_HOST_ARCH)))
>>> test -e debian/$$package.install.backup || cp debian/$$package.install debian/$$package.install.backup; \
>>> done
>>> sed -i '/mlx[45]/d' debian/ibverbs-providers.install debian/libibverbs-dev.install debian/rdma-core.install
>>> + sed -i '/efa/d' debian/ibverbs-providers.install debian/libibverbs-dev.install debian/rdma-core.install
>>> endif
>>> DESTDIR=$(CURDIR)/debian/tmp ninja -C build-deb install
>>>
>>>
>>>
>>> On Wed, Jul 10, 2019 at 11:37:01AM -0000, Debian buildds wrote:
>>>> * Source package: rdma-core
>>>> * Version: 24.0-1
>>>> * Architecture: armel
>>>> * State: failed
>>>> * Suite: sid
>>>> * Builder: antheil.debian.org
>>>> * Build log: https://buildd.debian.org/status/fetch.php?pkg=rdma-core&arch=armel&ver=24.0-1&stamp=1562758620&file=log
>>>>
>>>> Please note that these notifications do not necessarily mean bug reports
>>>> in your package but could also be caused by other packages, temporary
>>>> uninstallabilities and arch-specific breakages. A look at the build log
>>>> despite this disclaimer would be appreciated however.
>>
>> Was this error supposed to be reported by travis as well? I'm pretty sure all
>> tests passed.
>
> Did you get any build failure email from debian? I didn't.
I didn't, who is supposed to get these?
next prev parent reply other threads:[~2019-07-11 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <156275862123.1841.4329369138979653018@wuiet.debian.org>
2019-07-10 19:23 ` failed armel build of rdma-core 24.0-1 Jason Gunthorpe
2019-07-11 6:35 ` Gal Pressman
2019-07-11 7:07 ` Leon Romanovsky
2019-07-11 8:00 ` Gal Pressman [this message]
2019-07-11 11:11 ` Leon Romanovsky
2019-07-11 10:53 ` Benjamin Drung
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=bde8ef5c-10d4-0eae-efbf-5addff1633ff@amazon.com \
--to=galpress@amazon.com \
--cc=benjamin.drung@cloud.ionos.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.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