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

["Liao, TingtingX" <tingtingx.liao@intel.com>]

[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]

Hi  Patrick,

> 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?
This requires authorization from DPDK community maintainers.

> Why it is being used on your end. What are the "predictable risks?"
Sorry, this build option has been in our CI system for a long time.
And removing this option would pose unpredictable risks.
The next dpdk cycle is approaching, and in order to maintain the stability of the CI environment, the settings of the CI system cannot be modified arbitrarily.

Tingting Liao
________________________________
发件人: Patrick Robb <probb@iol.unh.edu>
发送时间: 2024年8月8日 20:37
收件人: Liao, TingtingX <tingtingx.liao@intel.com>
抄送: Juraj Linkeš <juraj.linkes@pantheon.tech>; Xu, HailinX <hailinx.xu@intel.com>; Cui, KaixinX <kaixinx.cui@intel.com>; ci@dpdk.org <ci@dpdk.org>
主题: Re: compilation|FAILURE| pw(142339) sid(32483) job(PER_PATCH_BUILD12580)[v8, 5/5] dts: add API doc generation

On Wed, Aug 7, 2024 at 11:28 PM Liao, TingtingX
<tingtingx.liao@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!

[-- Attachment #2: Type: text/html, Size: 5089 bytes --]