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

Hi,

The new LNT server instance http://lnt.llvm.org seems to fail in many cases.
Any entrance to a 'Run page' (e.g.
http://lnt.llvm.org/db_default/v4/nts/62475) and lately
also many perf bots result submissions (e.g.
http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2262/steps/test-suite/logs/stdio
) fails with:
"500 Internal Server Error".

Any ideas?

Thanks, Elad
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170731/d2d23703/attachment.html>

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.

- Matthias
> On Jul 31, 2017, at 12:10 AM, Cohen, Elad2 via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> Hi,
> 
> The new LNT server instance http://lnt.llvm.org
<http://lnt.llvm.org/> seems to fail in many cases.
> Any entrance to a ‘Run page’ (e.g.
http://lnt.llvm.org/db_default/v4/nts/62475
<http://lnt.llvm.org/db_default/v4/nts/62475>) and lately
> also many perf bots result submissions (e.g.
http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2262/steps/test-suite/logs/stdio
<http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2262/steps/test-suite/logs/stdio>
) fails with:
> “500 Internal Server Error”.
>  
> Any ideas?
>  
> Thanks, Elad
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
> 
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
> 
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
<http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170731/c382b6ca/attachment.html>

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:

http://lab.llvm.org:8011/builders/perf-x86_64-penryn-O3-polly-before-vectorizer-detect-only/builds/1205/steps/lnt.nightly-test/logs/stdio

2017-08-02 14:23:23 CRITICAL: Results were not obtained from submission.
nt
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-before-vectorizer-detect-only/tests/nt/build/sample-0/report.simple.csv
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-before-vectorizer-detect-only/tests/nt/build/sample-1/report.simple.csv
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-before-vectorizer-detect-only/tests/nt/build/sample-2/report.simple.csv
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-before-vectorizer-detect-only/tests/nt/build/sample-3/report.simple.csv
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-before-vectorizer-detect-only/tests/nt/build/sample-4/report.simple.csv
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-before-vectorizer-detect-only/tests/nt/build/sample-5/report.simple.csv
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-before-vectorizer-detect-only/tests/nt/build/sample-6/report.simple.csv
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-before-vectorizer-detect-only/tests/nt/build/sample-7/report.simple.csv
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-before-vectorizer-detect-only/tests/nt/build/sample-8/report.simple.csv
/home/grosser/buildslave/perf-x86_64-penryn-O3-polly-before-vectorizer-detect-only/tests/nt/build/sample-9/report.simple.csv
error: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>500 Internal Server Error</title>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error and was unable to complete
your request.  Either the server is overloaded or there is an error in
the application.</p>

2017-08-02 14:23:23 INFO: Running process cleanup.

Best,
Tobias

> 
> - Matthias
> 
> > On Jul 31, 2017, at 12:10 AM, Cohen, Elad2 via llvm-dev <llvm-dev
at lists.llvm.org> wrote:
> > 
> > Hi,
> > 
> > The new LNT server instance http://lnt.llvm.org
<http://lnt.llvm.org/> seems to fail in many cases.
> > Any entrance to a ‘Run page’ (e.g.
http://lnt.llvm.org/db_default/v4/nts/62475
<http://lnt.llvm.org/db_default/v4/nts/62475>) and lately
> > also many perf bots result submissions (e.g.
http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2262/steps/test-suite/logs/stdio
<http://lab.llvm.org:8014/builders/clang-native-arm-lnt-perf/builds/2262/steps/test-suite/logs/stdio>
) fails with:
> > “500 Internal Server Error”.
> >  
> > Any ideas?
> >  
> > Thanks, Elad
> > ---------------------------------------------------------------------
> > Intel Israel (74) Limited
> > 
> > This e-mail and any attachments may contain confidential material for
> > the sole use of the intended recipient(s). Any review or distribution
> > by others is strictly prohibited. If you are not the intended
> > recipient, please contact the sender and delete all copies.
> > 
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
<http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev