On Thu, Apr 5, 2018 at 9:28 AM, Satish Balay <[email protected]> wrote:
> On Thu, 5 Apr 2018, Matthew Knepley wrote: > > > > > > > http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/ > 2018/04/05/next.html > > > > I think I know all the fixes. I cannot do it until tonight at the > earliest. > > One of them, FETIDP, is an indentation fix. > > Once the fixes are in - I think it will take a few iterations [i.e a > few test cycles] to verify them [ and fix missing issues]. > > So assuming all fixes are pushed by tonight - [and you are able to > check build logs and fix issues immediately - and reschedule tests > immediately - we could do the release later tomorrow [but it might > push over to weekend/early-next week]. > > 1. Are few fix cycles by tomorrow feasible? [Matt] > Maybe, not sure > 2. Do these branches need to go into the release? [Matt] > No, it senseless to push it, but I do want a clean next as soon as we can. Matt > 3. Is it ok if the release gets pushed to early next week? [Barry, Todd] > > [assuming currently scheduled branches in next-tmp will be clean] > > thanks, > Satish > > > > [i.e the following branches still need fixes] > > > > origin/knepley/fix-dm-gmg > > > > origin/knepley/fix-ex62-tests > > > > origin/knepley/fix-fe-bd-integral > > > > origin/knepley/fix-fe-vector-spaces > > > > origin/knepley/fix-snes-ex69 > > > > origin/tisaac/feature-dmfield > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener https://www.cse.buffalo.edu/~knepley/ <http://www.caam.rice.edu/~mk51/>
