Skip to content

Commit 685c31c

Browse files
authored
Bump publish eventual consistency check timeout (again) (#4222)
## Motivation and Context <!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here --> crates.io team is aware of the issue: rust-lang/crates.io#11588 ---- _By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice._
1 parent 7ca3da9 commit 685c31c

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

tools/ci-build/publisher/src/subcommand/publish.rs

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -116,7 +116,11 @@ async fn is_published(index: Arc<CratesIndex>, handle: &PackageHandle) -> Result
116116

117117
/// Waits for the given package to show up on crates.io
118118
async fn wait_for_eventual_consistency(index: Arc<CratesIndex>, package: &Package) -> Result<()> {
119-
let max_wait_time = 60usize;
119+
// This timeout value is quite long (it started at 10 seconds), but is currently increased to handle
120+
// recent slowdowns we have seen with crates.io populating the sparse index. You can find some discussion
121+
// here: https://rust-lang.zulipchat.com/#narrow/channel/318791-t-crates-io/topic/sparse.20index.20updates.20sometimes.20being.20rate.20limited/with/529157932
122+
// and a tracking issue at https://github.com/rust-lang/crates.io/issues/11588
123+
let max_wait_time = 180usize;
120124
for _ in 0..max_wait_time {
121125
if !is_published(index.clone(), &package.handle).await? {
122126
tokio::time::sleep(Duration::from_secs(1)).await;

0 commit comments

Comments
 (0)