[OMPI devel] ompi github repository is NOT up to date

2014-10-05 Thread Gilles Gouaillardet
Folks,

currently, https://github.com/open-mpi/ompi last commit was 13 days ago
(see attached snapshot)

this is not the most up to date state !

for example, the last commit of my clone is

commit 54c839a970fc3025a08fe1c04b7d4b9767078264
Merge: dee6b63 5c5453b
Author: Gilles Gouaillardet 
List-Post: devel@lists.open-mpi.org
Date:   Fri Oct 3 11:57:33 2014 +0900

Merge branch 'topic/fix-pmix-native-getattr'

and if i remember correctly, some stuff has been commited after that
(though this was not reflected in my clone ...)

Could someone have a look at this ?
/* i am *not* a git guru and i do not have the most up to date clone */

in the mean time, i strongly advise everybody *not* to push anything to
the ompi repository

Cheers,

Gilles



Re: [OMPI devel] OMPI devel] OMPI devel] OMPI@GitHub: (Mostly) Open for business

2014-10-05 Thread Gilles Gouaillardet
Jeff,

i gave it a little thoughts and that does not seem to hard to achieve.

ghi https://github.com/stephencelis/ghi is a cli to manage (among other
things) labels, milestones and assignee

the elegant way would be to use webhooks and act accordingly
(short version: github issue a json request each time an issue is
modified to the web server of our choice)
and the "simple" way would be to write a cron script to do this

the first case means we have access to a public web server.
i have no experience in working with the IU folks, and though this is
the most technically elegant option,
there are some more political implications (who
manage/update/monitor/secure this).

the second option (cron script) could be accepted more easily by IU.

i will experiment on my sandbox from now.

Cheers,

Gilles

On 2014/10/03 22:20, Gilles Gouaillardet wrote:
> will do !
>
> Gilles
>
> "Jeff Squyres (jsquyres)"  wrote:
>> That's a possibility.  IU could probably host this for us.
>>
>> Would you mind looking into how hard this would be?
>>
>>
>> On Oct 3, 2014, at 8:41 AM, Gilles Gouaillardet 
>>  wrote:
>>
>>> Jeff,
>>>
>>> What about a bot using github's rich REST api that parses PR and 
>>> automatically sets label/milestone/assignee when a keyword is found ?
>>>
>>> for example :
>>> PR:milestone=v1.8.4:assignee=jsquyres:label=bug
>>> or
>>> #milestone=v1.8.4 #assignee=@jsquyres #label=bug
>>>
>>> i can investigate this way if needed
>>>
>>> Cheers,
>>>
>>> Gilles
>>>
>>> "Jeff Squyres (jsquyres)"  wrote:
 Gah.

 I just did some experimentation and confirmed this behavior:

 1. If you do not belong to a repo, you can file issues/pull requests and 
 comment on them.

 2. If you have *read* access to a repo, you can do everything from #1, but 
 you're also eligible for @mention auto-complete, and issues/pull requests 
 can be assigned to you.

 3. If you have *write* access to a repo, you can do everything from #2, 
 but you can also set labels, milestones, and assignees.

 All the OMPI devs have *read* access to ompi-release, meaning you can 
 create/comment on issues, but not set labels/milestones/assignees.

 I did not expect this behavior.  Grumble.  Will have to think about it a 
 bit...




 On Oct 3, 2014, at 7:07 AM, Gilles Gouaillardet 
  wrote:

> Jeff,
>
> my point is that label, milestone and assignee are *not* clickable for me 
> (see attached snapshot, "settings" icons are missing
>
> Cheers,
>
> Gilles
>
> On Fri, Oct 3, 2014 at 7:36 PM, Jeff Squyres (jsquyres) 
>  wrote:
> You can only assign a label and milestone, and assign the PR to someone, 
> *after* you create the PR (same with creating issues).
>
> See https://github.com/open-mpi/ompi/wiki/SubmittingBugs for details:
>
> 
>
>
>
>
> On Oct 2, 2014, at 11:37 PM, Gilles Gouaillardet 
>  wrote:
>
>
>> Jeff,
>>
>> i could not find how to apply a label to a PR via the web interface (and
>> i am not sure i can even do that since authority might be required)
>>
>> any idea (maybe a special keyword in the comment ...) ?
>>
>> Cheers,
>>
>> Gilles
>>
>> On 2014/10/03 1:53, Jeff Squyres (jsquyres) wrote:
>>> On Oct 2, 2014, at 12:47 PM, Ralph Castain  wrote:
>>>
 How are they going to review it, given they don't have authority to do 
 anything on that branch? Can they still comment? Can they reassign 
 them when done?
>>> Yes, they can comment.
>>>
>>> The idea was that they would apply the "reviewed" label when they have 
>>> reviewed it successfully.  These "reviewed" labels will then be easily 
>>> viewable in the PR listing by the RM/GK to know which ones are ready.
>>>
>> ___
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post: 
>> http://www.open-mpi.org/community/lists/devel/2014/10/15988.php
>
> -- 
> Jeff Squyres
> jsquy...@cisco.com
> For corporate legal information go to: 
> http://www.cisco.com/web/about/doing_business/legal/cri/
>
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/15990.php
>
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/15992.php

 -- 
 Jeff Squyres
 jsquy...@cisco.com
 For corporate legal information go t

Re: [OMPI devel] ompi github repository is NOT up to date

2014-10-05 Thread Ralph Castain
No, it's okay - for some reason, Mike's last commit is labelled as having been 
written 13 days ago. If you look at the commit log, you'll see that everything 
is just fine.

On Oct 5, 2014, at 7:47 PM, Gilles Gouaillardet  
wrote:

> Folks,
> 
> currently, https://github.com/open-mpi/ompi last commit was 13 days ago
> (see attached snapshot)
> 
> this is not the most up to date state !
> 
> for example, the last commit of my clone is
> 
> commit 54c839a970fc3025a08fe1c04b7d4b9767078264
> Merge: dee6b63 5c5453b
> Author: Gilles Gouaillardet 
> Date:   Fri Oct 3 11:57:33 2014 +0900
> 
>Merge branch 'topic/fix-pmix-native-getattr'
> 
> and if i remember correctly, some stuff has been commited after that
> (though this was not reflected in my clone ...)
> 
> Could someone have a look at this ?
> /* i am *not* a git guru and i do not have the most up to date clone */
> 
> in the mean time, i strongly advise everybody *not* to push anything to
> the ompi repository
> 
> Cheers,
> 
> Gilles
> 
> ___
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post: 
> http://www.open-mpi.org/community/lists/devel/2014/10/16009.php



Re: [OMPI devel] ompi github repository is NOT up to date

2014-10-05 Thread Jed Brown
Ralph Castain  writes:

> No, it's okay - for some reason, Mike's last commit is labelled as
> having been written 13 days ago. If you look at the commit log, you'll
> see that everything is just fine.

The commit was amended or rebased on Oct 5:

$ git log -1 --format=fuller
commit fd77ebd4525e9e0c1a3ab1c4966bf31aa45251b4
Author: Mike Dubman 
AuthorDate: Mon Sep 22 20:11:40 2014 +0300
Commit: Mike Dubman 
CommitDate: Sun Oct 5 14:33:56 2014 +0300

OSHMEM: sshmem verbs: allocate memory at fixed address

Use experimental verbs to allocate memory at fixed base
virtual address.

verbs will disqualify itself if shared_mr is disabled
or not supported and it is impossible to allocate memory
starting at fixed base virtual address.

verbs contig pages allocator did not guarantee fixed va, now it does.


pgpQAfCDAByfN.pgp
Description: PGP signature