Should it work for WIndows? If not disable it for that target.

You can do the builds locally to check things more easily: • Linux:

./packaging/build.sh -d <distro>

There are other issues too highlighted in the CI, e.g. CentOS 7 has the usual incorrect syntax for failure:

87.91 /src/plugins/out_logrotate/logrotate.c:800:9: error: 'for' loop initial declarations are only allowed in C99 mode
87.91          for (int j = i + 1; j < file_count; j++) {

You cannot declare variables as part of the loop definition for the C compiler available to vanilla CentOS 7. Note that this is also required for the coding standards: https://github.com/fluent/fluent-bit/blob/master/CONTRIBUTING.md#variable-definitions

I would suggest looking at the various build failures either in CI or repeating a build locally to see why. It looks to me like you need to tweak a few different things.

The OSS maintainers just do not have time to go through failing PRs unfortunately in any great detail, once it is green in CI then it can be reviewed.