MBED TRACE default level is INFO

[jeromecoutant]

Summary of changes

Current default trace level is DEBUG meaning all.
I think default trace level could be INFO, up to each user to manually set more details.

Impact of changes

Migration actions required

Documentation

---

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

---

[ciarmcom]

@jeromecoutant, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

[0xc0170]

@SeppoTakalo @AnttiKauppila @evedon @jamesbeyond Please review

[SeppoTakalo]

@teetak01 Does this affect client tests?

I'm OK to accept, but I don't know how many test cases rely on extra verbose trace level, so this might have regression on those..

[0xc0170]

I dont have details why debug was selected as default, info should be sufficient as a starting point.

[teetak01]

Looks ok. Our applications are already controlling the trace-levels when needed.

It would be good to make the same change also to https://github.com/armmbed/mbed-trace

[0xc0170]

CI started

[0xc0170]

CI internal error, will restart once fixed

cc @ARMmbed/mbed-os-test

[AnttiKauppila]

Maybe we could use even TRACE_LEVEL_ERROR as a default value

[evedon]

Seems reasonnable to start with INFO. Perhaps next step could be ERROR as Antti suggests.

[mbed-ci]

Test run: FAILED

Summary: 1 of 6 test jobs failed
Build number : 2
Build artifacts

Failed test jobs:

• jenkins-ci/mbed-os-ci_greentea-test