Ok - there something we are missing here.
Why would you want to do this?
Ray K
On 15/06/2018 10:11, chetan bhasin wrote:
Hi ,
For deployment , we want to replace assert with error log. Is there a
way in VPP to do that?
Thanks,
Chetan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messag
Hi,
I created a debugging patch set https://gerrit.fd.io/r/#/c/13122/ which
hints that there is something fishy going on with the python
virtualenv.
Per https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/12067/consol
e:
10:21:46 make -C test TEST_DIR=/w/workspace/vpp-verify-master-
ubuntu16
Actually assert is fine if we are doing QA testing but if we deploy build
at customer site we don't expect there would be a crash, even in error
condition, error code should be return and that code needs to be handled
properly.
Thanks,
Chetan Bhasin
On Tue, Jun 19, 2018, 14:32 Ray Kinsella wrot
See, for example, https://gerrit.fd.io/r/#/c/13061.
This failure is almost certainly unrelated to the patch. We need to fix this 90
seconds ago.
Thanks... Dave
13:02:17
==
13:02:17 ERROR: IP ACL test
13:02:17
---
Dave, et al,
Yes, all these are indications of the verify job running a different (and
cached) version of the Python VPP package than the one in build tree.
That stopped working as soon as I changed the in-tree one (and the caching
system picking up and apparently being stuck with a broken versi
On Jun 19, 2018, at 7:33 AM, Ole Troan
mailto:otr...@employees.org>> wrote:
Dave, et al,
Yes, all these are indications of the verify job running a different (and
cached) version of the Python VPP package than the one in build tree.
yup it certainly is...
That stopped working as soon as I c
ASSERT will not cause crash in production image, as it is excluded from
production builds.
However if ASSERT condition was met than it is good probability that VPP will
crash shortly after or start to misbehave.
> On 19 Jun 2018, at 04:28, chetan bhasin wrote:
>
> Actually assert is fine if we
Hi Ed,
> On 19 Jun 2018, at 17:24, Ed Kern (ejk) wrote:
>
>
>
>> On Jun 19, 2018, at 7:33 AM, Ole Troan wrote:
>>
>> Dave, et al,
>>
>> Yes, all these are indications of the verify job running a different (and
>> cached) version of the Python VPP package than the one in build tree.
>
> yu
I think what Ed meant to do is to speedup verify job without realizing
that test framework does a local install of vpp_papi package which is
part of the source tree.
this is correct.
So having cached virtualenv is a bad idea as
we see already.
dont agree…caching internal bits is certainly bad
Hi,
My colleague Liu Anhua has done the patch:
https://gerrit.fd.io/r/#/c/13134/
Couldn’t add Chengqiang as reviewer, gerrit says he/she can not be identified.
Regards,
Kingwel
From: Ni, Hongjun
Sent: Friday, June 08, 2018 5:54 PM
To: Edward Warnicke ; Kingwel Xie
; vpp-dev@lists.fd.io
Cc: Y
10 matches
Mail list logo
