Re: [PATCH] Add CI testing depends-on support status

[Aaron Conole <aconole@redhat.com>]

Patrick Robb <probb@iol.unh.edu> writes:

> Currently, the DPDK submission guidelines allow for contributors to
> indicate patch dependencies with their patchseries submission. This is
> not broadly supported in CI testing today, although we can expect this
> to change soon, as an initiative is about to begin with the goal of
> supporting patch dependencies on the patchwork server side. The DPDK
> Community Lab is going to allocate developer time towards this effort.
> Once that is complete, it should be relatively simple for the CI labs
> to begin supporting patch dependencies. In the meantime, it has been
> suggested that we begin tracking that support by lab. Once support is
> at 100%, this note on the testing page can be removed.
>
> Tested with local Hugo instance.
>
> Signed-off-by: Patrick Robb <probb@iol.unh.edu>
> ---

Acked-by: Aaron Conole <aconole@redhat.com>

>  content/testing/_index.md | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/content/testing/_index.md b/content/testing/_index.md
> index 394287b..b7d5e36 100644
> --- a/content/testing/_index.md
> +++ b/content/testing/_index.md
> @@ -103,6 +103,8 @@ referencing the report archive and incrementing one of the counters
>  A maintainer should wait the end of the tests (should be less than a day),
>  and check the results before accepting a patch.
>  
> +Note: At this time, the [depends-on](https://doc.dpdk.org/guides/contributing/patches.html#patch-dependencies) tag is supported in CI testing by only the Github Robot. Patchwork test reports under labels iol, intel, and loongson do not yet support this feature.
> +
>  #### Requesting a Patch Retest
>  
>  If CI reports a failure for a test label on Patchwork,