Failed Test Brief Log

[kuznetsovmoci]

Need the ability to quickly look at the output for failing tests to determine the root cause.

This view lists all of the platforms containing a failing test.
Consolidates information found across platforms as seen in the Brief view under Tests

[jwillemsen]

It is not clear to me what this exactly adds, is it a page with just the test part of the full log in a separate file (so the part of the file starting at http://scoreboard.ociweb.com/dds_doc_Latest_Micro_bee_win7_vc12_i1d0o1s1m1/2021_02_16_03_58_Full.html#section_6 and further), or something else?

[kuznetsovmoci]

It is not clear to me what this exactly adds, is it a page with just the test part of the full log in a separate file (so the part of the file starting at http://scoreboard.ociweb.com/dds_doc_Latest_Micro_bee_win7_vc12_i1d0o1s1m1/2021_02_16_03_58_Full.html#section_6 and further), or something else?

This new report combines individual "Brief" reports for all failed Tests, grouped by the server. It is intended to be a one-click summary of all failed tests. It is a time-saving alternative to clicking through all Test "Brief" links on the main page.

[jwillemsen]

How does this work with scoreboards that don't pull all logs locally, for example http://www.dre.vanderbilt.edu/scoreboard/integrated.html only has links and doesn't cache all logs of all builds, those are stored at the various locations, with a lot of builds (including huge valgrind logs) it costs a lot of bandwidth and diskspace, it uses the -b option of the scoreboard script.

[jwillemsen]

For the git commit you could use diffroot to construct a hyperlink to github, see the ACE/TAO scoreboard

[mitza-oci]

How does this work with scoreboards that don't pull all logs locally, for example http://www.dre.vanderbilt.edu/scoreboard/integrated.html only has links and doesn't cache all logs of all builds, those are stored at the various locations, with a lot of builds (including huge valgrind logs) it costs a lot of bandwidth and diskspace, it uses the -b option of the scoreboard script.

Seems like the new feature could just be disabled when -b is used.

[kuznetsovmoci]

How does this work with scoreboards that don't pull all logs locally, for example http://www.dre.vanderbilt.edu/scoreboard/integrated.html only has links and doesn't cache all logs of all builds, those are stored at the various locations, with a lot of builds (including huge valgrind logs) it costs a lot of bandwidth and diskspace, it uses the -b option of the scoreboard script.

Seems like the new feature could just be disabled when -b is used.

Implemented

[jwillemsen]

Get this error when generating our axcioma scoreboard

Not enough arguments for Prettify::Process at /home/build/jenkins/workspace/fc_axcioma_scoreboard/autobuild/command/process_logs.pm line 279, near "$log_file)"
Compilation failed in require at /home/build/jenkins/workspace/fc_axcioma_scoreboard/autobuild/autobuild.pl line 83 (#1)
    (F) The function requires more arguments than you specified.
    
Uncaught exception from user code:
	Not enough arguments for Prettify::Process at /home/build/jenkins/workspace/fc_axcioma_scoreboard/autobuild/command/process_logs.pm line 279, near "$log_file)"
	Compilation failed in require at /home/build/jenkins/workspace/fc_axcioma_scoreboard/autobuild/autobuild.pl line 83.

[jwillemsen]

Command we use is $WORKSPACE/autobuild/scoreboard.pl -b -n -f $DOC_ROOT/x11-scoreboard/axcioma.xml -y $DOC_ROOT/x11-scoreboard/custom.css -o index.html -d $LOG_ROOT -v

axcioma.xml can be found at https://github.com/RemedyIT/scoreboard

[jwillemsen]

@mitza-oci @kuznetsovmoci Can you have a look at the error I got when using the updated autobuild?

[kuznetsovmoci]

I ve created new PR with the fix: https://github.com/DOCGroup/autobuild/pull/35/files

…

On Thu, Feb 18, 2021 at 11:54 AM Johnny Willemsen ***@***.***> wrote: @mitza-oci <https://github.com/mitza-oci> @kuznetsovmoci <https://github.com/kuznetsovmoci> Can you have a look at the error I got when using the updated autobuild? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANHDG34LP6PUFQYXZSDOOPLS7VH43ANCNFSM4XPWWZPQ> .