Re: [petsc-dev] git worktree

2021-05-19 Thread Scott Kruger
On 2021-05-19 08:36, Patrick Sanan did write: > Cool - I didn't know about this approach - If you still have your experiments > sitting around, can you put numbers on what kind of space savings are we > talking about vs the dumb approach (I have an independent clone for every > branch I'm

Re: [petsc-dev] git worktree

2021-05-19 Thread Barry Smith
Lawrence, Oh, I always use that, (even now) my prompt is miles long. Didn't help me at all, I still messed up constantly; my brain ignores what my eyes clearly see. I need more than a clear sign post telling me where I am, I need a hammer that hits me whenever I do something wrong in

Re: [petsc-dev] git worktree

2021-05-19 Thread Lawrence Mitchell
> On 19 May 2021, at 15:38, Barry Smith wrote: > > I tried the multiple clone approach first but found I was constantly > thinking I was in a different branch than I was in as I went between clones > and messing up my working directory and getting confused and frustrated. So I >

Re: [petsc-dev] Mat test ex238

2021-05-19 Thread Barry Smith
I will submit an MR to reduce the CI time, sorry about this. I'm not sure why I ended up with such a big CI test case, probably just sloppiness. > On May 19, 2021, at 6:11 AM, Matthew Knepley wrote: > > This is taking hundreds of seconds in every run. For the CI, shouldn't we > reduce the

Re: [petsc-dev] git worktree

2021-05-19 Thread Barry Smith
I tried the multiple clone approach first but found I was constantly thinking I was in a different branch than I was in as I went between clones and messing up my working directory and getting confused and frustrated. So I developed some of my tools because I was unable to utilize my brain

Re: [petsc-dev] Mat test ex238

2021-05-19 Thread Stefano Zampini
+1 The help says for timing tests, but it makes no sense to me for them being part of the entire CI We should probably have a dedicated runner for performance regressions (running only performance runs, something like requires: performance) Not sure why the sizes are so large, probably Barry wants

[petsc-dev] Mat test ex238

2021-05-19 Thread Matthew Knepley
This is taking hundreds of seconds in every run. For the CI, shouldn't we reduce the size of the matrix, maybe to 5000 instead of 5? Thanks, Matt -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which

Re: [petsc-dev] git worktree

2021-05-19 Thread Patrick Sanan
Cool - I didn't know about this approach - If you still have your experiments sitting around, can you put numbers on what kind of space savings are we talking about vs the dumb approach (I have an independent clone for every branch I'm interested in working on simultaneously)? @Barry - thanks