From 6aab0ebcbcd5d6af000d8595fd1ab892fa07845e Mon Sep 17 00:00:00 2001 From: Brandon Hancock Date: Wed, 31 Jul 2024 10:12:37 -0400 Subject: [PATCH] Remove overly complicated test --- src/crewai/pipeline/pipeline.py | 2 +- tests/pipeline/test_pipeline.py | 6 ------ 2 files changed, 1 insertion(+), 7 deletions(-) diff --git a/src/crewai/pipeline/pipeline.py b/src/crewai/pipeline/pipeline.py index 6b4bac450..58d75dd58 100644 --- a/src/crewai/pipeline/pipeline.py +++ b/src/crewai/pipeline/pipeline.py @@ -53,7 +53,7 @@ Pipeline Terminology: - Trace: The journey of an individual input through the entire pipeline. Example pipeline structure: -crew1 >> crew2 >> crew3 +crew1 >> crew2 >> crew3 This represents a pipeline with three sequential stages: 1. crew1 is the first stage, which processes the input and passes its output to crew2. diff --git a/tests/pipeline/test_pipeline.py b/tests/pipeline/test_pipeline.py index dcdd49efe..7ed68fcb4 100644 --- a/tests/pipeline/test_pipeline.py +++ b/tests/pipeline/test_pipeline.py @@ -334,12 +334,6 @@ async def test_pipeline_with_parallel_stages_end_in_single_stage(mock_crew_facto assert pipeline_result_1.token_usage == expected_token_usage -@pytest.mark.asyncio -async def test_pipeline_with_parallel_stages_multiple_inputs(mock_crew_factory): - # TODO: implement - pass - - def test_pipeline_rshift_operator(mock_crew_factory): """ Test that the >> operator correctly creates a Pipeline from Crews and lists of Crews.