absolutebi/serai
1
0
Fork 0
mirror of https://github.com/serai-dex/serai.git synced 2025-12-08 20:29:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Don't clear cache within a batch build

Browse Source 
A caller *can* call batch from a threaded environment and still trigger this at
this time. I'm unsure that use case exists/matters.

If GITHUB_CI is set, build in two batches to try and avoid storage limits.
This commit is contained in:
Luke Parker
2023-11-27 03:25:25 -05:00
parent 9da1d714b3
commit aa666afc08
2 changed files with 25 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
tests/full-stack/src/lib.rs
View File

@@ -32,13 +32,21 @@ pub struct Handles {
}
pub async fn full_stack(name: &str) -> (Handles, Vec<TestBodySpecification>) {
let mut docker_names = serai_processor_tests::docker_names(NetworkId::Bitcoin);
docker_names.append(&mut serai_processor_tests::docker_names(NetworkId::Monero));
docker_names.extend([
let mut processor_docker_names = serai_processor_tests::docker_names(NetworkId::Bitcoin);
processor_docker_names.extend(serai_processor_tests::docker_names(NetworkId::Monero));
let mut docker_names = vec![
serai_message_queue_tests::docker_name(),
serai_coordinator_tests::serai_docker_name(),
serai_coordinator_tests::coordinator_docker_name(),
]);
];
// If this is in the GH CI, build in two stages so we don't hit storage limits
if std::env::var("GITHUB_CI").is_ok() {
serai_docker_tests::build_batch(processor_docker_names).await;
} else {
docker_names.extend(processor_docker_names);
}
serai_docker_tests::build_batch(docker_names).await;
let (coord_key, message_queue_keys, message_queue_composition) = message_queue_instance().await;