llvm dev - Aug 2017 - [LNT] new server instance http://lnt.llvm.org seems unstable

> On Aug 2, 2017, at 12:43 PM, Tobias Grosser <tobias.grosser at
inf.ethz.ch> wrote:
> 
> On Tue, Aug 1, 2017, at 00:33, Matthias Braun via llvm-dev wrote:
>> The run page problem were triggered by one of my commits (sorry) and
>> should be mitigated now, see the thread at
>> http://lists.llvm.org/pipermail/llvm-dev/2017-July/115971.html
>> <http://lists.llvm.org/pipermail/llvm-dev/2017-July/115971.html>
>> 
>> I don't know about the submission problems, could they just an
occasional
>> network problem or are they a common phenomenon? Chris did some
>> improvements to LNT to report back problems from the server side rather
>> than a generic "500 internal server error" in case of errors.
This should
>> become active the next time lnt.llvm.org <http://lnt.llvm.org/>
is
>> updated.
> 
> Just FYI, I still see such errors on the most recent bui;lds:
Seems it is something else then, someone needs to inspect the server logs to
find out more about what is going on.

- Matthias

OK, who is in charge?

Best,
Tobias

On Wed, Aug 2, 2017, at 21:45, Matthias Braun via llvm-dev
wrote:
> 
> > On Aug 2, 2017, at 12:43 PM, Tobias Grosser <tobias.grosser at
inf.ethz.ch> wrote:
> > 
> > On Tue, Aug 1, 2017, at 00:33, Matthias Braun via llvm-dev wrote:
> >> The run page problem were triggered by one of my commits (sorry)
and
> >> should be mitigated now, see the thread at
> >> http://lists.llvm.org/pipermail/llvm-dev/2017-July/115971.html
> >>
<http://lists.llvm.org/pipermail/llvm-dev/2017-July/115971.html>
> >> 
> >> I don't know about the submission problems, could they just an
occasional
> >> network problem or are they a common phenomenon? Chris did some
> >> improvements to LNT to report back problems from the server side
rather
> >> than a generic "500 internal server error" in case of
errors. This should
> >> become active the next time lnt.llvm.org
<http://lnt.llvm.org/> is
> >> updated.
> > 
> > Just FYI, I still see such errors on the most recent bui;lds:
> 
> Seems it is something else then, someone needs to inspect the server logs
> to find out more about what is going on.
> 
> - Matthias
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

Chris is on vacation this week. Not sure if someone else has access to the
logs...

- Matthias
> On Aug 2, 2017, at 12:45 PM, Tobias Grosser <tobias.grosser at
inf.ethz.ch> wrote:
> 
> OK, who is in charge?
> 
> Best,
> Tobias
> 
> On Wed, Aug 2, 2017, at 21:45, Matthias Braun via llvm-dev wrote:
>> 
>>> On Aug 2, 2017, at 12:43 PM, Tobias Grosser <tobias.grosser at
inf.ethz.ch> wrote:
>>> 
>>> On Tue, Aug 1, 2017, at 00:33, Matthias Braun via llvm-dev wrote:
>>>> The run page problem were triggered by one of my commits
(sorry) and
>>>> should be mitigated now, see the thread at
>>>> http://lists.llvm.org/pipermail/llvm-dev/2017-July/115971.html
>>>>
<http://lists.llvm.org/pipermail/llvm-dev/2017-July/115971.html>
>>>> 
>>>> I don't know about the submission problems, could they just
an occasional
>>>> network problem or are they a common phenomenon? Chris did some
>>>> improvements to LNT to report back problems from the server
side rather
>>>> than a generic "500 internal server error" in case of
errors. This should
>>>> become active the next time lnt.llvm.org
<http://lnt.llvm.org/> is
>>>> updated.
>>> 
>>> Just FYI, I still see such errors on the most recent bui;lds:
>> 
>> Seems it is something else then, someone needs to inspect the server
logs
>> to find out more about what is going on.
>> 
>> - Matthias
>> 
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev