We see the following warnings on o3:

# /var/log/openqa
[2022-04-25T09:17:28.805933Z] [warn] [pid:8752] /var/lib/openqa/share/tests/obs/needles is not a git directory
[2022-04-25T09:45:21.130734Z] [warn] [pid:29759] /var/lib/openqa/share/tests/obs/needles is not a git directory
[2022-04-25T09:51:16.928704Z] [warn] [pid:32010] /var/lib/openqa/share/tests/obs/needles is not a git directory
[2022-04-25T09:59:06.379418Z] [warn] [pid:1890] /var/lib/openqa/share/tests/obs/needles is not a git directory
[2022-04-25T10:05:23.079609Z] [warn] [pid:9221] /var/lib/openqa/share/tests/obs/needles is not a git directory

More context for the last one:

[2022-04-25T10:05:23.021959Z] [info] [pid:9221] Running cmd: git -C /var/lib/openqa/share/tests/obs log --stat --pretty=oneline --abbrev-commit --no-merges dd41ad936f8deb0f38400a26cf2bb6e4ca909e93..4928900e3ff4a75a18bbb5f5e6ddf0ae7992eb5a
[2022-04-25T10:05:23.048900Z] [debug] [pid:9221] b7ff8ae Move ruby tests into a branch specific Makefile
 tests/rspec_webui_tests.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
0f78bed Move installation etc. to a Makefile in the branch
 tests/rspec_webui_tests.pm | 11 +++--------
 1 file changed, 3 insertions(+), 8 deletions(-)
[2022-04-25T10:05:23.049215Z] [info] [pid:9221] cmd returned 0
[2022-04-25T10:05:23.049622Z] [info] [pid:9221] Running cmd: timeout 20 git -C /var/lib/openqa/share/tests/obs diff --stat dd41ad936f8deb0f38400a26cf2bb6e4ca909e93..4928900e3ff4a75a18bbb5f5e6ddf0ae7992eb5a
[2022-04-25T10:05:23.077203Z] [debug] [pid:9221]  tests/rspec_webui_tests.pm | 11 +++--------
 1 file changed, 3 insertions(+), 8 deletions(-)
[2022-04-25T10:05:23.077519Z] [info] [pid:9221] cmd returned 0
[2022-04-25T10:05:23.079609Z] [warn] [pid:9221] /var/lib/openqa/share/tests/obs/needles is not a git directory

Reproduced by: https://openqa.opensuse.org/tests/2315662#investigation (DISTRI=obs)

The needles directory is not a git repo on its own, but just a needles/ subdirectory in the distri repo. (I wonder why we haven't seen this log message before.)

Rollback steps¶

• Revert https://github.com/os-autoinst/openqa-logwarn/pull/33

Acceptance criteria¶

• AC1: The case is handled instead of resulting in a warning

Suggestions¶

• Confirm that the code already works as intended and the warnings may be pointless
• Maybe this is a warning that can be ignored or handled