[Scummvm-git-logs] scummvm-sites director-buildbot -> 851b9a4a4eaf8eb73571bc06eb91376623ba2ce6

[rvanlaar]

This automated email contains information about 1 new commit which have been
pushed to the 'scummvm-sites' repo located at https://github.com/scummvm/scummvm-sites .

Summary:
851b9a4a4e Add logging on if change is director related


Commit: 851b9a4a4eaf8eb73571bc06eb91376623ba2ce6
    https://github.com/scummvm/scummvm-sites/commit/851b9a4a4eaf8eb73571bc06eb91376623ba2ce6
Author: Roland van Laar (roland at rolandvanlaar.nl)
Date: 2023-01-16T14:44:48+01:00

Commit Message:
Add logging on if change is director related

PR 4546 [1] had director related changes. Somehow a build wasn't
kicked off. Logging showed that a buildrequest wasn't injected
after calling `file_is_director_related`.

The working hypothesis is the `Change` didn't include the files.
To test this logging is added to show all files and whether or
not a build was triggered for it.

[1] https://github.com/scummvm/scummvm/pull/4546

Changed paths:
    master.py


diff --git a/master.py b/master.py
index dd73a72..be258fe 100644
--- a/master.py
+++ b/master.py
@@ -82,9 +82,13 @@ def file_is_director_related(change: Change) -> bool:
     log.msg("###################### CHANGE")
     log.msg(f"{change}")
     for name in change.files:
+        log.msg(f"Checking file: {name}")
         for check in checks:
+            log.msg(f"Checking check: {check}")
             if check in name:
+                log.msg(f"Change is director related with file: {name} for check: {check}")
                 return True
+    log.msg("Changes are not director related")
     return False