On 15/05/2023 11:25, Mauro Carvalho Chehab wrote: > Em Mon, 15 May 2023 09:46:41 +0200 > Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> escreveu: > >> Hi Krzysztof, >> >> On Sun, May 14, 2023 at 1:01 PM Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote: >>> On 10/05/2023 10:05, Mauro Carvalho Chehab wrote: >>>> And another CI job testing bisect breakages as I receive pull requests, >>>> applying patch per patch and using both allyesconfig and allmodconfig, >>>> also on x86_64 arch with W=1: >>>> >>>> https://builder.linuxtv.org/job/patchwork/ >>>> >>>> The rule is to not merge stuff on media tree if any of those jobs >>>> fail. I also fast-forward merging patches whose subject states that >>>> the build has failed. >>>> >>>> In order to help with that, on normal situation, I usually take one week >>>> to merge stuff from media_stage into media_tree, doing rebases at >>>> media_stage if needed to avoid git bisect build breakages at media_tree >>>> (which is from where I send my update PRs to you). >>>> >>>> Unfortunately, currently we don't have resources to do multiple randconfig >>> >>> Is you media staging tree included in LKP (kernel test robot)? You would >>> get huge build coverage after every push to your staging repo. > > No idea, as I don't know where LKP settings are stored, nor what frequency > it is doing builds from git://linuxtv.org/media_stage.git, if any. Do you know > where we can check such configuration? AFAIR, it checks all kernel.org repos, but anything outside should be manually added. See: https://github.com/intel/lkp-tests/pull/271 I actually proposed a talk around this for LPC, so it seems it might be useful. > > In the end, patches there will end going to linux-next, so at least some > sort of coverage is there, but I'm not sure if LKP will always reply to > linux-media if the patch causing build regressions is there. > > While being helpful, one problem with LKP is that it is hard to filter out > reports per git tree. The only way to check if the report is applicable to > media trees seems to be looking inside the e-mail's body. If you setup specific repo entry in LKP, you will get a quite specific email, e.g. with subject: [krzk:for-next] BUILD SUCCESS 5b248db78d1aa679009efa4763794890572e63fb [krzk-github:n/of-device-id-of-match-ptr-rebase] BUILD SUCCESS ce0964f4 (where krzk/krzk-github are the names of repos in LKP) Best regards, Krzysztof
