[petsc-dev] nightly build repositories not getting properly updated

[Barry Smith]

  Damn we have no mechanism that moves stuff that has been merged into next into master so master falls behind and then people base new features on outdated master code …..

   Can we have a script that emails us each morning a list of branches in next that are not in master and links to the nightly test page so we can quickly check if they broke something in next?  And either fix them or get them into master since they work.

   Barry



On Nov 17, 2013, at 10:05 PM, Satish Balay <balay at mcs.anl.gov> wrote:

> On Sun, 17 Nov 2013, Barry Smith wrote:
> 
>> 
>> Build on n-gage arch-opensolaris-misc /export/home/petsc/petsc.clone-2 November 17, 2013 03:09:06 PM CST 
>> Cleaning throughly at /export/home/petsc/petsc.clone-2
>> HEAD is now at 9f236db Merge branch 'knepley/fix-plex-regression'
>> Currently building git branch: remotes/origin/HEAD
>> commit 9f236db7cf9dbb108598d7c519960b98572e186e
>> Merge: 6925468 7cc78b8
>> Author: Matthew G. Knepley <knepley at gmail.com>
>> Date:   Wed Nov 13 11:46:39 2013 -0600
>> 
>>    Merge branch 'knepley/fix-plex-regression'
>> 
>> 
>> Run today but last update was 4 days ago. Not a very useful test.
> 
> But that was the latest state of master as of few hours back [when the
> test was ran]
> 
> Satish
> 
> 
>> 
>> I think you need to add a check in dashboard on each repository that it is actually up to date to start testing? And complain otherwise we could be testing outdated stuff for months.
>> 
>> 
>>  Barry