akshaychitneni commented on code in PR #2244: URL: https://github.com/apache/datafusion-ballista/pull/2244#discussion_r3759866864
########## dev/chaos-kind.sh: ########## @@ -0,0 +1,170 @@ +#!/bin/bash + +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. + +# Run the chaos harness's Kubernetes (kind) scenarios locally. +# +# dev/chaos-kind.sh [command] [-- <extra args passed to cargo test>] +# +# Commands: +# up Create the kind cluster (if missing), build + load the chaos images. +# test Run the kind chaos scenarios against the current cluster. +# all up + test (default) +# down Delete the kind cluster. +# +# Env: +# CLUSTER_NAME kind cluster name (default: ballista-chaos) +# KEEP_CLUSTER if "0", `all` deletes the cluster when done (default: 1, keep) +# +# Examples: +# dev/chaos-kind.sh # build, (re)create, load, run everything +# dev/chaos-kind.sh up # just stand the cluster up +# dev/chaos-kind.sh test -- --nocapture # re-run tests on an existing cluster +# dev/chaos-kind.sh down # tear it down + +set -euo pipefail + +CLUSTER_NAME=${CLUSTER_NAME:-ballista-chaos} +KEEP_CLUSTER=${KEEP_CLUSTER:-1} Review Comment: Not needed here. CHAOS_CONCURRENT_TASKS is consumed by the executor pods via their manifest env, not by the harness process -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
