From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: "Daniel Sangorrin" References: <62079D2F712F7747B0BDCC6821B8DF0D013DDDF9@G08CNEXMBPEKD02.g08.fujitsu.local> In-Reply-To: <62079D2F712F7747B0BDCC6821B8DF0D013DDDF9@G08CNEXMBPEKD02.g08.fujitsu.local> Date: Fri, 24 Aug 2018 12:11:04 +0900 Message-ID: <006501d43b58$17f3c700$47db5500$@toshiba.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Language: ja Subject: Re: [Fuego] Problem of adding a benchmark result table List-Id: Mailing list for the Fuego test framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "'Li, Xiaoming'" , fuego@lists.linuxfoundation.org Hi Li, > On Behalf Of Li, Xiaoming > I want to add a table of building results for every single benchmark = in Jenkins. If you want to use a table to show the building results instead of a = plot, you can change the chart_type from chart_config.json to = testset_summary_table. If you run the benchmark again, you should get a = table instead of a plot. That functionality is implemented at: scripts/parser/prepare_chart_data.py scripts/mod.js I believe that code needs some improvements: - ability to override chart_config.json with a per-board = configuration - I have seen in Dhrystone that the table shows pass=3D1 but also = err=3D1 - The tables only show building results (pass/fail), you may want to = add the benchmark measures > My solutions is to use jenkins's plugin groovy postbuild, which can = add a hyperlink > in build history. > But groovy postbuild requies jenkins=E2=80=98s version of 2.6.0 or = later, as fuego's default is > 2.32.1. Updating jenkins regularly is important. However, we have had bad = experiences with Jenkins' plugins. Each time we upgraded Jenkins a = number of plugins where not available anymore causing many breakages. = For that reason, we decided to limit the usage of plugins to the minimum = necessary. > I also have to install java8 to run higher version jenkins. This would require changing the Dockerfile. It might be a hard job if it = can't be done with Debian Jessie. > Could anyone give me a better idea? Apart from using chart_config.son, there is another option. We have an = SQL-like interface to fetch results from Fuego. You can use that = interface with ftc gen-report and create an html/xls/pdf report with all = of the build results that you want. Maybe you could even call to ftc = gen-report in a postbuild action and then add a link to the generated = html from the "Set build description" post action. Also, soon we will be able to post test results to kernelci and squad = instances. Best regards, Daniel > -------------------------------------------------- >=20 > Li, Xiaoming >=20 > Development Dept.III >=20 > Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST) No. 6 Wenzhu = Road, Nanjing, > 210012, China >=20 > TEL: +86+25-86630566-8451 >=20 > FAX: +86+25-83317685 >=20 > MAIL: lixm.fnst@cn.fujitsu.com >=20 > -------------------------------------------------- >=20 >=20