compilation|FAILURE| pw(142339) sid(32483) job(PER_PATCH_BUILD12580)[v8, 5/5] dts: add API doc generation

Patrick Robb probb at iol.unh.edu
Thu Aug 8 14:37:10 CEST 2024


On Wed, Aug 7, 2024 at 11:28 PM Liao, TingtingX
<tingtingx.liao at intel.com> wrote:
>
> Hi Juraj,
>
> Sorry, we cannot modify the parameters of CI apply patch without authorization.
> The doc directory is used to store documents and does not support code submission.
> Based on the special circumstances of your patch, you can directly contact the community maintainer to decide whether to merge this patch.
>

Okay, I agree that if needed we can just talk to the maintainers, do a
manual test for this patch, and they can merge based on the results of
manual testing.

But, what authorization are you referring to, for modifying the build
options? Do you mean it needs to be authorized by DPDK maintainers, or
by the CI community, or by someone at Intel STV team? We are not using
this build option at the UNH CI testing lab, which is why I want to
understand better why it is being used on your end. What are the
"predictable risks?"

Sorry for taking up your time. I also want to make sure that we at UNH
are not using a bad process!


More information about the ci mailing list