From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH rdma-core] Add a .travis.yml file
Date: Thu, 6 Oct 2016 10:10:09 -0600 [thread overview]
Message-ID: <20161006161009.GE1224@obsidianresearch.com> (raw)
In-Reply-To: <20161006045337.GK9282-2ukJVAZIZ/Y@public.gmane.org>
On Thu, Oct 06, 2016 at 07:53:37AM +0300, Leon Romanovsky wrote:
> > I don't understand how a compiler can be too new? The next round of
> > rolling release distros are likely to use this compiler, and those are
> > the distros that will first pick to up rdma-core.
>
> I have an issue in front of my eyes where kernel fails to build with old
> gcc version, while new gcc version works.
Heh, last week I had the opposite..
> My experience shows the same, however I want to minimize the test burden
> on the users.
IMHO, it is more valuable to run a build on the full distro stack than
to try and inject old compiler variations into travis. Old system
libraries are just as likely to fail a build as the compiler.
I don't have any way to do that automatically. IMHO Travis is not able to
handle that sort of workload.
Perhaps a pre-release pass through OBS or something like it is the answer here?
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-10-06 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 23:28 [PATCH rdma-core] Add a .travis.yml file Jason Gunthorpe
[not found] ` <1475105337-18002-1-git-send-email-jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-09-29 15:20 ` Doug Ledford
[not found] ` <57ED3128.4060509-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-09-29 16:25 ` Jason Gunthorpe
2016-10-05 11:51 ` Leon Romanovsky
[not found] ` <20161005115132.GE9282-2ukJVAZIZ/Y@public.gmane.org>
2016-10-05 16:32 ` Jason Gunthorpe
[not found] ` <20161005163250.GB18636-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-06 4:53 ` Leon Romanovsky
[not found] ` <20161006045337.GK9282-2ukJVAZIZ/Y@public.gmane.org>
2016-10-06 16:10 ` Jason Gunthorpe [this message]
[not found] ` <20161006161009.GE1224-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2016-10-06 17:52 ` Leon Romanovsky
2016-10-05 16:39 ` Bart Van Assche
[not found] ` <0de7bc15-5e2e-8240-ba84-a5a95dcb2834-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-10-06 4:58 ` Leon Romanovsky
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=20161006161009.GE1224@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.