Commit 144fbfc
committed
BF(TST): use caplog instead of capfd for testing if we log a warning
for some reason on my laptop capfd failed to provide desired effect. May be because
I am running pytest with -s ;) will not investigate -- using caplog is the more
kosher way for this purpose, and allows for control of the logging level we would like
to have to ensure that the message is output1 parent 8d85f14 commit 144fbfc
1 file changed
+4
-3
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
85 | 85 | | |
86 | 86 | | |
87 | 87 | | |
88 | | - | |
| 88 | + | |
89 | 89 | | |
90 | 90 | | |
91 | 91 | | |
92 | 92 | | |
93 | 93 | | |
| 94 | + | |
| 95 | + | |
94 | 96 | | |
95 | 97 | | |
96 | 98 | | |
| |||
101 | 103 | | |
102 | 104 | | |
103 | 105 | | |
104 | | - | |
105 | 106 | | |
106 | | - | |
| 107 | + | |
107 | 108 | | |
108 | 109 | | |
109 | 110 | | |
| |||
0 commit comments