Workaround for make test:all DEBUG=1

[zvecr]

Description

Should address the keyboard level issues seen in 23041.

Compiling: quantum/quantum.c                                                                       In file included from quantum/quantum.h:54,
                 from quantum/quantum.c:17:
quantum/logging/debug.h:58:9: error: expected identifier or ‘(’ before ‘do’
   58 |         do {                                                      \
      |         ^~
quantum/logging/debug.h:60:11: error: expected identifier or ‘(’ before ‘while’
   60 |         } while (0)
      |           ^~~~~
quantum/logging/debug.h:58:9: error: expected identifier or ‘(’ before ‘do’
   58 |         do {                                                      \
      |         ^~
quantum/logging/debug.h:60:11: error: expected identifier or ‘(’ before ‘while’
   60 |         } while (0)
      |           ^~~~~
 [ERRORS]
 | 
 | 
 | 
make[1]: *** [builddefs/common_rules.mk:373: .build/test_obj/basic/quantum/quantum.o] Error 1

Longer term the plan is to rework logging to remove dprintf.

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Issues Fixed or Closed by This PR

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[DavidSannier]

Hello Joel,
Thanks for this fix.
It is not exactly in the same area, but I have another comment about this DEBUG=1:
As this DEBUG value is used with CFLAGS += -g$(DEBUG) in common_rules.mk, it could also be set to 2 or 3, but in build_test.mk, it is only compared to 1 (meaning that CONSOLE_ENABLE won't be set for those values).
Regards

[zvecr]

It is not exactly in the same area, but I have another comment about this DEBUG=1:
As this DEBUG value is used with CFLAGS += -g$(DEBUG) in common_rules.mk, it could also be set to 2 or 3, but in build_test.mk, it is only compared to 1 (meaning that CONSOLE_ENABLE won't be set for those values).

Looks like an oversight. Feel free to raise a PR to address the issue.

[DavidSannier]

#23097