[llvm-dev] [LNT] new server instance http://lnt.llvm.org seems unstable (original) (raw)

Matthias Braun via llvm-dev llvm-dev at lists.llvm.org
Wed Aug 2 12:51:30 PDT 2017


Actually I just remember LNT has a page for viewing the log:

http://lnt.llvm.org/log

... OperationalError: (OperationalError) (2006, 'MySQL server has gone away') 'SELECT NT_Run.ID AS NT_Run_ID, NT_Run.MachineID AS NT_Run_MachineID, NT_Run.OrderID AS NT_Run_OrderID, NT_Run.ImportedFrom AS NT_Run_ImportedFrom, NT_Run.StartTime AS NT_Run_StartTime, NT_Run.EndTime AS NT_Run_EndTime, NT_Run.SimpleRunID AS NT_Run_SimpleRunID, NT_Run.Parameters AS NT_Run_Parameters \nFROM NT_Run \nWHERE NT_Run.ID = %s' (62996L,) ...

Not sure what is causing that or what to do about it though.

On Aug 2, 2017, at 12:47 PM, Tobias Grosser <tobias.grosser at inf.ethz.ch> wrote:

It's not super urgent, just wanted to make sure it does not get lost. I CC Chris to make sure he has a full inbox when coming back from vacation. ;-) @Chris, hope you have a good and relaxed stay. Best, Tobias On Wed, Aug 2, 2017, at 21:46, Matthias Braun wrote: 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



More information about the llvm-dev mailing list