FW: [EXT] Re: Fw: kernelci report issue

FW: [EXT] Re: Fw: kernelci report issue

[Srinivas Dubasi]

[-- Attachment #1.1: Type: text/plain, Size: 4147 bytes --]

Hi,

Greetings!.

In general, do you trigger on all the boards available or on specific boards @ lab-nxp?

Kernel CI Dashboard - Tests Reports - next/master next-20220323 baseline<https://linux.kernelci.org/test/job/next/branch/master/kernel/next-20220323/plan/baseline/>
(4 boards in kernelci report of next-20220323).

Would like to understand so that, we will make sure all the boards are available and in good state.


[cid:image001.png@01D83F9C.18E94B20]
Regards,
Srinivas

From: Suram Suram <suram@nxp.com>
Sent: Thursday, March 24, 2022 2:21 PM
To: Srinivas Dubasi <srinivas.dubasi@nxp.com>
Subject: Fw: [EXT] Re: Fw: kernelci report issue

FYI
________________________________
From: Suram Suram <suram@nxp.com<mailto:suram@nxp.com>>
Sent: Friday, September 18, 2020 8:52 AM
To: Kevin Hilman <khilman@baylibre.com<mailto:khilman@baylibre.com>>
Subject: Re: [EXT] Re: Fw: kernelci report issue

Hi Kevin,
Thank you very much for the reply.
As suggested, we will post it to the group.

Regards
Suram
________________________________
From: Kevin Hilman <khilman@baylibre.com<mailto:khilman@baylibre.com>>
Sent: Thursday, September 17, 2020 9:05 PM
To: Suram Suram <suram@nxp.com<mailto:suram@nxp.com>>
Subject: [EXT] Re: Fw: kernelci report issue

Caution: EXT Email

Hi Suram,

Could you or the original engineer report these issues to
kernelci@groups.io<mailto:kernelci@groups.io>?  We are aware of part of this issue but not all of
it.  I'm not working on the web frontend, so it would be helpful to
get this report on the list.

Thanks,

Kevin


On Wed, Sep 16, 2020 at 10:42 PM Suram Suram <suram@nxp.com<mailto:suram@nxp.com>> wrote:
>
> Hi Kevin,
> A request/ feedback for improving the user experience of kernelci.org.
> Please see the email below from one of our engineers who will be tracking the status of the runs on kernelci and take appropriate actions.
>
> This was discovered when our local boot test failed and wanted to check the status on kernelci.org.
> Can you please look into this and see if the user experience can be improved.
>
> Thank you very much.
>
> Regards
> Suram
> ________________________________
> From: Aisheng Dong <aisheng.dong@nxp.com<mailto:aisheng.dong@nxp.com>>
> Sent: Monday, September 14, 2020 3:31 PM
> To: Suram Suram <suram@nxp.com<mailto:suram@nxp.com>>
> Cc: Tv Rao T <tv.rao@nxp.com<mailto:tv.rao@nxp.com>>
> Subject: kernelci report issue
>
>
> Hi Suram,
>
>
>
> i.MX Local Upstream daily test reported some upstream kernel boot failures.
>
> I checked with kernelci has the same issue. However, the kernelci report seems not to be that clear.
>
>
>
> From the log below, you can see MX6Q Sabresd board boot hanged and result is "FAIL"
>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstorage.kernelci.org%2Fnext%2Fmaster%2Fnext-20200911%2Farm%2Fimx_v6_v7_defconfig%2Fgcc-8%2Flab-nxp%2Fbaseline-imx6q-sabresd.html&amp;data=02%7C01%7Csuram%40nxp.com%7Cbb32661686024eb5a18708d85b1f4f42%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637359537314002765&amp;sdata=yuCRLzvAw4PgT0BbrzyXhnrD4SIoMYxZPyOB12fVtSg%3D&amp;reserved=0
>
> Boot log: imx6q-sabresd
>
> Warnings: 0
>
> Kernel Warnings: 0
>
> Errors: 0
>
> Boot result: FAIL
>
> Kernel Errors: 0
>
>
>
> But from the the kernelci main page below, it didn't show those failures.
>
> I guess they were categorized as 'Unknown' issues. However, even those failures were marked as "Unknown" issues, another problem is that users has no way to
>
> Quickly filter out those 'Unknown' issues because the 'Unknown' button is grey.
>
> Can you help check those two issues and report to kernelci if it can be improved?
>
>
>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkernelci.org%2Fsoc%2Fimx%2Fjob%2Fnext%2Fkernel%2Fnext-20200911%2Fplan%2Fbaseline%2F&amp;data=02%7C01%7Csuram%40nxp.com%7Cbb32661686024eb5a18708d85b1f4f42%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637359537314002765&amp;sdata=bKlWsnEtECtZ9fjyYlmwzBxuCCjxxfdhrwwEncFQTzc%3D&amp;reserved=0
>
>
>
> Regards
>
> Aisheng

[-- Attachment #1.2: Type: text/html, Size: 10251 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 139066 bytes --]

Re: FW: [EXT] Re: Fw: kernelci report issue

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 375 bytes --]

On Thu, Mar 24, 2022 at 10:57:50AM +0000, Srinivas Dubasi wrote:

> In general, do you trigger on all the boards available or on specific
> boards @ lab-nxp?

KernelCI will submit jobs for all boards that it knows about which it
has access to and knows about, it does need to have a configuration for
each device type.  There's no specific filter configured for the NXP
lab.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: FW: [EXT] Re: Fw: kernelci report issue

[Srinivas Dubasi]

Hi,

Thanks for the clarification.

Regards,
Srinivas

-----Original Message-----
From: Mark Brown <broonie@kernel.org> 
Sent: Thursday, March 24, 2022 6:25 PM
To: kernelci@groups.io; Srinivas Dubasi <srinivas.dubasi@nxp.com>
Cc: Kevin Hilman <khilman@baylibre.com>
Subject: Re: FW: [EXT] Re: Fw: kernelci report issue

On Thu, Mar 24, 2022 at 10:57:50AM +0000, Srinivas Dubasi wrote:

> In general, do you trigger on all the boards available or on specific 
> boards @ lab-nxp?

KernelCI will submit jobs for all boards that it knows about which it has access to and knows about, it does need to have a configuration for each device type.  There's no specific filter configured for the NXP lab.