Ferruh Yigit <ferruh.yi...@intel.com> writes:

> On 4/27/2020 12:24 PM, Somalapuram, Amaranath wrote:
>> Hi Ferruh,
>> 
>> Do you want me to resubmit. 
>
> Hi Amaranath,
>
> No need to send a new version.
>
>> 
>> I see this below errors email:
>> 
>> From: ro...@bytheb.org
>> 
>> Test-Label: travis-robot
>> Test-Status:
>> https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpdk.org%2Fpatch%2F69359&amp;data=02%7C01%7CAmaranath.Somalapuram%40amd.com%7C3c14b94fb68e492d035608d7ea93e6a2%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637235793258422338&amp;sdata=WcqAv8%2BRhMq4z0YRZ9S09NuV8x7kjgc2TtX3jmvJlzA%3D&amp;reserved=0
>> 
>> _Travis build: errored_
>> Build URL:
>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftravis-ci.com%2Fovsrobot%2Fdpdk%2Fbuilds%2F162163735&amp;data=02%7C01%7CAmaranath.Somalapuram%40amd.com%7C3c14b94fb68e492d035608d7ea93e6a2%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637235793258422338&amp;sdata=plABOXG44ijGqIo5CHCHWerbirVOlf5hujOFiWkysb4%3D&amp;reserved=0
>
> The travis error seems unrelated [1], cc'ed David and Aaron for it.

I agree.

> [1] Two issues reported
> a) ninja: build stopped: Error writing to build log: Disk quota
> exceeded.

This occurs on some of the ARM64 builds.  Travis is aware of the issue,
but don't seem urgently fixing it. :-/  I think we have a series
outstanding that should be applied to drop those builds for now.

> b) No output has been received in the last 10m0s, this potentially indicates a
> stalled build or something wrong with the build itself.

This is a future enhancement I need to work on.  When a build has jobs
that are stalled / errored, we need to restart them (at least once).  Or
otherwise flag it.  It especially happens when internal travis
infrastructure fails.

>
> Also community lab tests seems failing because of the mellanox performance
> report, but this patch is not something that can affect the performance.
> Cc'ed Raslan & Ali and lab for it.
> https://lab.dpdk.org/results/dashboard/patchsets/10717/
>
>> 
>> Regards,
>> S.Amarnath
>> 
>> -----Original Message-----
>> From: Ferruh Yigit <ferruh.yi...@intel.com> 
>> Sent: Monday, April 27, 2020 4:29 PM
>> To: Kumar, Ravi1 <ravi1.ku...@amd.com>; Somalapuram, Amaranath
>> <amaranath.somalapu...@amd.com>; dev@dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH v1] maintainers: update for AMD xgbe and ccp 
>> crypto
>> 
>> [CAUTION: External Email]
>> 
>> On 4/27/2020 7:14 AM, Kumar, Ravi1 wrote:
>>> [AMD Public Use]
>>>
>>> Acked-by: Ravi Kumar <ravi1.ku...@amd.com>
>>>> -----Original Message-----
>>>> From: Somalapuram, Amaranath <amaranath.somalapu...@amd.com>
>>>> Sent: Monday, April 27, 2020 11:42 AM
>>>> To: dev@dpdk.org
>>>> Cc: Kumar, Ravi1 <ravi1.ku...@amd.com>
>>>> Subject: [PATCH v1] maintainers: update for AMD xgbe and ccp crypto
>> 
>> I guess net driver is called 'axgbe', good to fix while merging.
>> 
>>>>
>>>> From: Amaranath Somalapuram <amaranath.somalapu...@amd.com>
>>>>
>>>> Ownership change.
>>>>
>>>> Signed-off-by: Amaranath Somalapuram <amaranath.somalapu...@amd.com>
>>>> ---
>>>> MAINTAINERS | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>>> index d31a80929..c3dcedbb3 100644
>>>> --- a/MAINTAINERS
>>>> +++ b/MAINTAINERS
>>>> @@ -566,7 +566,7 @@ F: doc/guides/nics/ena.rst
>>>> F: doc/guides/nics/features/ena.ini
>>>>
>>>> AMD axgbe
>>>> -M: Ravi Kumar <ravi1.ku...@amd.com>
>>>> +M: Somalapuram Amaranath <asoma...@amd.com>
>>>> F: drivers/net/axgbe/
>>>> F: doc/guides/nics/axgbe.rst
>>>> F: doc/guides/nics/features/axgbe.ini
>>>> @@ -953,7 +953,7 @@ T: git://dpdk.org/next/dpdk-next-crypto
>>>> F: doc/guides/cryptodevs/features/default.ini
>> 
>> Thanks Ravi, Welcome Somalapuram.
>> 
>> Acked-by: Ferruh Yigit <ferruh.yi...@intel.com>
>> 
>>>>
>>>> AMD CCP Crypto
>>>> -M: Ravi Kumar <ravi1.ku...@amd.com>
>>>> +M: Somalapuram Amaranath <asoma...@amd.com>
>>>> F: drivers/crypto/ccp/
>>>> F: doc/guides/cryptodevs/ccp.rst
>>>> F: doc/guides/cryptodevs/features/ccp.ini
>>>> --
>>>> 2.17.1
>>>>
>> 

Reply via email to