Comment out the chain_workflows example in the functional tests script (

flyteorg#72)

Signed-off-by: Eduardo Apolinario <eapolinario@users.noreply.github.com>

Signed-off-by: Eduardo Apolinario <eapolinario@users.noreply.github.com>
Signed-off-by: Eduardo Apolinario <653394+eapolinario@users.noreply.github.com>
Co-authored-by: Eduardo Apolinario <eapolinario@users.noreply.github.com>

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.