Hi,
We are seeing a VPP crash (ASSERT) with following stack trace, when we try to
create a DPO from within a VPP worker.
The below crash clear shows that DPO creation is restricted only to the main
thread, since the ASSERT is making sure that the thread id is 0.
* Backtrace of "Thread workers
Hi, guys!
How can i show all current configurations and save it？
Someone can help me? Thx
Best Regeards,
Xiaopeng
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14993): https://lists.fd.io/g/vpp-dev/message/14993
Mute This Topic:
I agree with Damjan on this.
Seems convoluted to comprehend and enhance the suite. I think, it isn’t very
intuitive. But I guess we are tied to python to interface with the tools
(scapy, trex, blah for traffic profiles)?
--
Regards,
Balaji.
From: on behalf of "Damjan Marion via
+1, simple is key here
I think that we simply should remove that tap test as it falls under device
driver tests which we don't test in make test framework.
PS I really don't like direction where test framework is going,
originally it was very simple to write tests even without having python
I would just as soon keep the story as simple as possible. “sudo make
test[-debug]” => run both test-runner and vpp privileged. “make test[-debug]”
means run neither one privileged.
FWIW... Dave
From: Paul Vinciguerra
Sent: Saturday, December 28, 2019 12:22 PM
To: Dave Barach (dbarach)
Cc:
Coverity run failed today.
Current number of outstanding issues are 2
Newly detected: 0
Eliminated: 0
More details can be found at
https://scan.coverity.com/projects/fd-io-vpp/view_defects
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14989):
