What version of Open MPI are you running?
The error is indicating that Open MPI is trying to start a user-level helper
daemon on the remote node, and the daemon is seg faulting (which is unusual).
One thing to be aware of:
https://www.open-mpi.org/faq/?category=building#install-overwrite
Jeff Squyres (jsquyres), on Wed 08 Feb 2017 15:19:58 +, wrote:
> 1. You reverted an actual grammar fix: "support" -> "supported".
Oops, I missed that part, sorry.
> 2. I don't think that "likely" is bad to have. Like I said above, the test
> itself is just a switch/case test based on a
The email script doesn't run on GitHub.
We have a GitHub web hook that fires out to the Open MPI hostgator instance
(our web hosting provider). That fires up a PHP script (i.e., GitHub calls
https://...open-mpi.org/...php) and funnels it the information about the
commits that were just pushed
FWIW, I didn't get the commit email either, and I am pretty sure it's
not the first time it happens. There are no archives for this ML, do we
have a way to see the logs of the emailing script that runs on github ?
Brice
Le 08/02/2017 16:19, Jeff Squyres (jsquyres) a écrit :
> On Feb 7, 2017,
On Feb 8, 2017, at 10:15 AM, gil...@rist.or.jp wrote:
>
> iirc, i saw build being cancelled (i was monitoring the Jenkins console)
> when new commits were pushed (or force pushed) to the current PR
>
> i will make a test tomorrow
Oh, sweet. That would be good to know; thanks!
> it is fair
Jeff,
iirc, i saw build being cancelled (i was monitoring the Jenkins console)
when new commits were pushed (or force pushed) to the current PR
i will make a test tomorrow
it is fair that using Travis for new PR is very likely more useful than
for validating all builds
Cheers,
Gilles
-
On Feb 8, 2017, at 9:34 AM, gil...@rist.or.jp wrote:
>
> i also noted that each time a PR is updated, a new Travis build is
> started.
> on the other hand, Jenkins is a bit smarter and does not build or cancel
> "obsolete" PR.
Are you sure?
Here's how I thought Jenkins worked:
- create a PR:
Jeff,
i also noted that each time a PR is updated, a new Travis build is
started.
on the other hand, Jenkins is a bit smarter and does not build or cancel
"obsolete" PR.
i think most of us cannot manually direct Travis to cancel a given build.
fwiw, building pushes is not useless.
we recently
I noticed the other evening that we are doing two things at Travis:
1. Building pull requests
2. Building pushes
The 2nd one might well be contributing to our backlog (i.e., every time a PR is
merged to the ompi repo, we Travis build again).
I also confirmed with Travis that we're supposed to
