Comment out the chain_workflows example in the functional tests script (

flyteorg#72) Signed-off-by: Eduardo Apolinario <[email protected]> Signed-off-by: Eduardo Apolinario <[email protected]> Signed-off-by: Eduardo Apolinario <[email protected]> Co-authored-by: Eduardo Apolinario <[email protected]>
eapolinario · Sep 23, 2022 · 8004373 · 8004373
1 parent 9aef1f7
commit 8004373
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/boilerplate-repo/boilerplate/flyte/end2end/run-tests.py b/boilerplate-repo/boilerplate/flyte/end2end/run-tests.py
@@ -27,7 +27,8 @@
     ],
     "core": [
         ("core.flyte_basics.deck.wf", {}),
-        ("core.control_flow.chain_entities.chain_workflows_wf", {}),
+        # The chain_workflows example in flytesnacks expects to be running in a sandbox.
+        # ("core.control_flow.chain_entities.chain_workflows_wf", {}),
         ("core.control_flow.dynamics.wf", {"s1": "Pear", "s2": "Earth"}),
         ("core.control_flow.map_task.my_map_workflow", {"a": [1, 2, 3, 4, 5]}),
         # Workflows that use nested executions cannot be launched via flyteremote.