con/tinuous not getting all PRs builds?

[yarikoptic]

I thought to look at logs of #111 but I do not find them on smaug:

(git)smaug:/mnt/datasets/datalad/ci/git-annex[master]git
$> ls builds/2022/03
cron-20220301/  cron-20220306/  cron-20220311/  cron-20220316/  cron-20220321/  cron-20220326/
cron-20220302/  cron-20220307/  cron-20220312/  cron-20220317/  cron-20220322/  cron-20220327/
cron-20220303/  cron-20220308/  cron-20220313/  cron-20220318/  cron-20220323/  cron-20220328/
cron-20220304/  cron-20220309/  cron-20220314/  cron-20220319/  cron-20220324/  manual-20220322/
cron-20220305/  cron-20220310/  cron-20220315/  cron-20220320/  cron-20220325/  pr-102/

so there is only logs for #102 and none for #111

even after completing a fresh con/tinuous run

```shell datalad@smaug:~$ flock -n -E 0 /home/datalad/.run/tinuous-git-annex.lock /mnt/datasets/datalad/ci/git-annex/tools/cron_job { "resources": { "core": { "limit": 5000, "used": 208, "remaining": 4792, "reset": 1648479639 }, "search": { "limit": 30, "used": 0, "remaining": 30, "reset": 1648478892 }, "graphql": { "limit": 5000, "used": 2, "remaining": 4998, "reset": 1648481437 }, "integration_manifest": { "limit": 5000, "used": 0, "remaining": 5000, "reset": 1648482432 }, "source_import": { "limit": 100, "used": 0, "remaining": 100, "reset": 1648478892 }, "code_scanning_upload": { "limit": 1000, "used": 0, "remaining": 1000, "reset": 1648482432 }, "actions_runner_registration": { "limit": 10000, "used": 0, "remaining": 10000, "reset": 1648482432 }, "scim": { "limit": 15000, "used": 0, "remaining": 15000, "reset": 1648482432 } }, "rate": { "limit": 5000, "used": 208, "remaining": 4792, "reset": 1648479639 } } 2022-03-28T10:47:12-0400 [INFO ] tinuous tinuous 0.5.1+3.ga2b297e 2022-03-28T10:47:13-0400 [INFO ] tinuous Fetching resources from github 2022-03-28T10:47:13-0400 [INFO ] tinuous Fetching runs newer than 2022-03-28 03:38:38+00:00 2022-03-28T10:47:13-0400 [INFO ] tinuous Fetching runs for workflow .github/workflows/build-macos.yaml (Build git-annex on macOS) 2022-03-28T10:47:14-0400 [INFO ] tinuous Fetching runs for workflow .github/workflows/build-ubuntu.yaml (Build git-annex on Ubuntu) 2022-03-28T10:47:14-0400 [INFO ] tinuous Fetching runs for workflow .github/workflows/build-windows.yaml (Build git-annex on Windows) 2022-03-28T10:47:15-0400 [INFO ] tinuous Fetching releases newer than 2022-03-28 03:38:38+00:00 2022-03-28T10:47:15-0400 [INFO ] tinuous Release 8.20210903 is draft; skipping 2022-03-28T10:47:15-0400 [INFO ] tinuous Release 8.20210803 is draft; skipping 2022-03-28T10:47:15-0400 [INFO ] tinuous Release 8.20210714 is draft; skipping 2022-03-28T10:47:15-0400 [INFO ] tinuous Release 8.20210630 is draft; skipping 2022-03-28T10:47:15-0400 [INFO ] tinuous 0 logs downloaded 2022-03-28T10:47:15-0400 [INFO ] tinuous 0 artifacts downloaded 2022-03-28T10:47:15-0400 [INFO ] tinuous 0 release assets downloaded ```

any ideas @jwodder ?

[jwodder]

@yarikoptic tinuous is configured in tinuous.yaml to only fetch workflow logs for build-macos.yaml, build-ubuntu.yaml, and build-windows.yaml, while #111 used build-linux-buildenv.yaml. Note that, if you were to add build-linux-buildenv.yaml to the config, only future runs would be captured by tinuous, so #111 would still not be downloaded (unless you manually messed with the state file).

[yarikoptic]

It is ok to just look into the future, thank you in advance!

[jwodder]

Added build-linux-buildenv.yaml to config.

[yarikoptic]

coolio, I see

(git)smaug:/mnt/datasets/datalad/ci/git-annex/builds/2022/03[master]
$> ls -l pr-111 
total 0
drwxr-sr-x 1 datalad datalad 62 Mar 28 12:55 build-linux-buildenv.yaml-11-2b5de141-success/
drwxr-sr-x 1 datalad datalad 62 Mar 28 11:55 build-linux-buildenv.yaml-9-26a69594-failed/

now so should be ok