Coverage remained the same at 64.667% when pulling c9a7585bb711a356bd579fa50443acce5db5c084 on updated-logging into 871aa088aacba4e268d44f50bbc1f43ed405a84d on 0.x.
Coverage remained the same at 64.667% when pulling ee49e463e93b9e06895835c6eff763bb377a948f on updated-logging into 871aa088aacba4e268d44f50bbc1f43ed405a84d on 0.x.
Coverage remained the same at 64.667% when pulling ddcbbaf9573ec519b89368497df568f042a22845 on updated-logging into 871aa088aacba4e268d44f50bbc1f43ed405a84d on 0.x.
Tweaking the way logging is working from #47 (ref #45)