transient failure. works now.
On Tue, May 24, 2022 at 10:13 PM Mark Adams wrote:
> I was working on Crusher yesterday and I think I rebased over main and now
> I am hanging here.
>
> Any ideas?
>
> (gdb) bt
> #0 0x7fff81bd5547 in sched_yield () from /lib64/libc.so.6
> #1 0x7fff79e43665
It would be nice if when people received MR review requests it indicated if
the review was trivial and could be done in a minute or two. Then maybe quick
ones could flow through the system faster.
How do people 1) know first when they have things they should (or have been
asked to) review
On Wed, May 25, 2022 at 11:55 AM Barry Smith wrote:
>
> It would be nice if when people received MR review requests it indicated
> if the review was trivial and could be done in a minute or two. Then maybe
> quick ones could flow through the system faster.
>
> How do people 1) know first when
I guess one could use tags to indicate the complexity of the review?
I personally would like a weekly digest of MRs that I have been requested to
review with clickable links. The dashboard would also be helpful.
All the best, Todd.
From: petsc-dev on behalf of Matthew Knepley
Date: Wednesda
> if there was a dashboard at Gitlab where we could see what is pending for us.
There is — though it is somewhat hidden.
In the top right on gitlab there is a drop-down list with the “merge-branch”
symbol that usually has a number highlighted in orange. Clicking on that should
produce a drop-do
On Wed, 25 May 2022, Matthew Knepley wrote:
> On Wed, May 25, 2022 at 11:55 AM Barry Smith wrote:
>
> >
> > It would be nice if when people received MR review requests it indicated
> > if the review was trivial and could be done in a minute or two. Then maybe
> > quick ones could flow through
Does the email requesting a review include the tags somewhere in it? If so,
this is a great idea.
Weekly, don't you mean hourly? It is possible to set up a crontab on your
system to query gitlab and process the result and send an email to you. But it
is a bit involved to setup and maintain
> On May 25, 2022, at 12:06 PM, Satish Balay wrote:
>
> On Wed, 25 May 2022, Matthew Knepley wrote:
>
>> On Wed, May 25, 2022 at 11:55 AM Barry Smith wrote:
>>
>>>
>>> It would be nice if when people received MR review requests it indicated
>>> if the review was trivial and could be done
On Wed, 25 May 2022, Barry Smith wrote:
>
>
> > On May 25, 2022, at 12:06 PM, Satish Balay wrote:
> >
> > On Wed, 25 May 2022, Matthew Knepley wrote:
> >
> >> On Wed, May 25, 2022 at 11:55 AM Barry Smith wrote:
> >>
> >>>
> >>> It would be nice if when people received MR review requests i
* WARNING *
erf() not found
=
I am fine with leaving that in the log
Matt
On Wed, May 25, 2022 at 4:40 PM Barry Smith wrote:
>
> * WARNING *
>erf() not found
>
>
But removing from printing to the screen? Boy cries wolf business if we print
too much stuff to screen and this seems very trivial to print to screen.
> On May 25, 2022, at 4:41 PM, Matthew Knepley wrote:
>
> I am fine with leaving that in the log
>
> Matt
>
> On Wed, May 25, 2022 at 4:
On Wed, May 25, 2022 at 5:09 PM Barry Smith wrote:
>
> But removing from printing to the screen? Boy cries wolf business if we
> print too much stuff to screen and this seems very trivial to print to
> screen.
>
It will be in the log because the results of all these tests will be in the
log.
13 matches
Mail list logo
