Commit fd648e7
committed
ci: run async integration tests against baikal in niquests fallback job
The async-niquests job only ran unit tests (test_async_davclient.py),
missing the niquests+Baikal combination entirely. This exposes a bug
where niquests digest auth fails with
AttributeError: 'coroutine' object has no attribute 'history'
because auth.py:345 calls r.connection.send() without awaiting it.
Add Baikal as a service and extend the test run to cover
test_async_integration.py -k baikal so CI catches this regression.
prompt: async tests towards baikal is currently broken locally - but the
github workflow run passes successfully. Is it regressions in the niquests
library, or are the baikal tests not run at github? Use `gh` tool to get
logs from the github runs. rather look into how we can get the async
integration tests running at github - I've made a new branch for it.
Apply and commit.1 parent 432e336 commit fd648e7
1 file changed
Lines changed: 29 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
338 | 338 | | |
339 | 339 | | |
340 | 340 | | |
| 341 | + | |
| 342 | + | |
| 343 | + | |
| 344 | + | |
| 345 | + | |
| 346 | + | |
| 347 | + | |
| 348 | + | |
| 349 | + | |
| 350 | + | |
| 351 | + | |
341 | 352 | | |
342 | 353 | | |
343 | 354 | | |
| |||
347 | 358 | | |
348 | 359 | | |
349 | 360 | | |
| 361 | + | |
| 362 | + | |
| 363 | + | |
| 364 | + | |
| 365 | + | |
| 366 | + | |
| 367 | + | |
| 368 | + | |
| 369 | + | |
| 370 | + | |
| 371 | + | |
| 372 | + | |
| 373 | + | |
| 374 | + | |
| 375 | + | |
350 | 376 | | |
351 | 377 | | |
352 | 378 | | |
| |||
356 | 382 | | |
357 | 383 | | |
358 | 384 | | |
359 | | - | |
| 385 | + | |
| 386 | + | |
| 387 | + | |
360 | 388 | | |
361 | 389 | | |
362 | 390 | | |
| |||
0 commit comments