Commit ceff058
authored
vortex-file: Spawn tasks via runtime instead of directly via tokio (#8711)
## Rationale for this change
I upgraded to 0.78 and some automation we have that detects when
dependencies use raw `tokio::spawn` got triggered. We need to control
all spawn points, both for correctness testing and for instrumentation
purposes. I realize that these spawns are in test code, but I thought
since vortex already has the runtime abstractions, it wouldn't hurt to
use them in the tests as well (admittedly our tooling is not crazily
sophisticated so it can't distinguish whether it's testing code or not).
## What changes are included in this PR?
Use `TokioRuntime` instead of raw `tokio::spawn` in tests.
## What APIs are changed? Are there any user-facing changes?
n/a
Signed-off-by: Frederic Branczyk <fbranczyk@gmail.com>1 parent a649d75 commit ceff058
1 file changed
Lines changed: 5 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
468 | 468 | | |
469 | 469 | | |
470 | 470 | | |
| 471 | + | |
471 | 472 | | |
472 | 473 | | |
473 | 474 | | |
474 | 475 | | |
475 | 476 | | |
476 | | - | |
| 477 | + | |
477 | 478 | | |
478 | 479 | | |
479 | 480 | | |
| |||
488 | 489 | | |
489 | 490 | | |
490 | 491 | | |
491 | | - | |
| 492 | + | |
492 | 493 | | |
493 | 494 | | |
494 | 495 | | |
| |||
557 | 558 | | |
558 | 559 | | |
559 | 560 | | |
| 561 | + | |
560 | 562 | | |
561 | 563 | | |
562 | 564 | | |
563 | | - | |
| 565 | + | |
564 | 566 | | |
565 | 567 | | |
566 | 568 | | |
| |||
0 commit comments