ci: disable tuning test when runing ASAN (#5770)

The tuning test relies on a predictable execution environment. It
assumes that spawning a new task can complete reasonably fast. When
running tests with ASAN, the tuning test will spurriously fail. After
investigating, I believe this is due to running tests with ASAN enabled
and without `release` in a low resource environment (CI) results in an
execution environment that is too slow for the tuning test to succeed.
This commit is contained in:
Carl Lerche
2023-06-06 09:35:19 -07:00
committed by GitHub
parent 1204da7300
commit 779b9c19d5
2 changed files with 4 additions and 5 deletions
+1 -2
View File
@@ -35,7 +35,6 @@ fn single_thread() {
}
#[test]
#[cfg(not(tokio_cross))]
fn many_oneshot_futures() {
// used for notifying the main thread
const NUM: usize = 1_000;
@@ -595,7 +594,7 @@ async fn test_block_in_place4() {
// is sufficient. If there is a regression, this test will hang. In theory, we
// could add limits, but that would be likely to fail on CI.
#[test]
#[cfg(not(tokio_cross))]
#[cfg(not(tokio_no_tuning_tests))]
fn test_tuning() {
use std::sync::atomic::AtomicBool;
use std::time::Duration;