This has gone a little off the original topic. Do we want to run the CI tests as an unprivileged user (something as simple as su to a vpp user) or just let the community be aware that the CI test results are different than when run locally?
But as to Damjan's and Blaji's comments, I agree. I personally don't like the framework either. From my perspective, it forces *way* too much on the user. My preference is a declarative over programmatic configuration. As an example, I have seen Dave and Andrew both contribute tests where they build an array of commands and fire them off to the cli via the api. To me, that seems like a waste of effort, when vpp provides the ability to exec a script via startup. And you all have put *way* too much effort into complying with the way the test framework decided that you have to modify the startup config. I would rather see you be able to work the way you normally would. in my mind, one should be able to specify a __startup_conf__ = " " string and not have to rely on constructs such as extra_vpp_punt_config and extra_vpp_plugin_config. Paul
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#15023): https://lists.fd.io/g/vpp-dev/message/15023 Mute This Topic: https://lists.fd.io/mt/69288694/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
