[openib-general] OpenSM Issues of the last couple days

[Eitan Zahavi]

Hi Sasha,

 

Without another devel branch I will not be able to test patches before 
the make it into the trunk.

I do not know how to make an automatic mail extraction into patches into 
tree such that I can have automatic patch check.

 

I am not a great fan of a new branch too.

So we need to agree that regression runs resulting with bug reporting 
post commit to the trunk is our mode of work.

I do not have a big issue with this (but it is more work for Hal).

Eitan

Sasha Khapyorsky wrote:
> On 18:42 Fri 08 Dec     , Eitan Zahavi wrote:
>   
>> Instead on relying on bug reading I use automatic regression. I wish we 
>> could agree on some regression that
>> each developer will have to run before patches are committed to the trunk.
>> On my side I would love to have an automatic way to include all the 
>> patches posted (one at a time) run "dead or alive" check
>> and provide feedback. Currently my automation is limited to testing the 
>> trunk. So I will always be complaining after the patches are
>> committed. I think this is the way most other components testing works.
>>
>> What kind of regression suite do you and Sasha use?
>>     
>
> On my side it clearly depends from kind of changes. In general I would
> call this "uni-testing".
>
>   
>> Can we agree on minimal pre-commit testing?
>> Can we have a branch for that sake where all patches will first have to 
>> go into for 2 days? (it will allow for pre-trunk testing).
>>     
>
> One more development branch? Will you test (or even see) this? If so I
> can publish the "fresh" tree.
>
> Sasha
>
> _______________________________________________
> openib-general mailing list
> openib-general at openib.org
> http://openib.org/mailman/listinfo/openib-general
>
> To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
>