#!/bin/bash

# Copyright (c) 2018 Red Hat, Inc.
#
# Licensed 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.

set -eu

zuul_work_dir=$1

# Use cd in the script rather than chdir from the script module. The chdir
# has some source-code comments that indicate for script that it needs to be
# an absolute path. Since our zuul_work_dir defaults to
# "{{ zuul.project.src_dir }}" in many places, that could be rather bad.
# The script can ensure it starts from the home dir and then change into the
# directory, which should work for both relative and absolute paths.
cd $HOME
cd $zuul_work_dir

# A non zero exit code means we didn't find any stestr or testr database
# content. Additionally if the database content is parseable we emit on
# stdout the commands which can be used to retrieve that parsed content.
# This distiction is necessary as we want to take different actions based
# on whether or not the database content is parseable.
rc=1
commands=""

if [[ -d .testrepository ]] ; then
    rc=0
    commands="testr ${commands}"
fi

if [[ -d .stestr ]] ; then
    rc=0
    # NOTE(mordred) Check for the failing file in the .stestr directory
    # instead of just the directory. A stestr run that fails due to python
    # parsing errors will leave a directory but with no test results, which
    # will result in an error in the subunit generation phase.
    if [[ -f .stestr/failing ]] ; then
        commands="stestr ${commands}"
    fi
fi

# Add all the tox envs to the path so that type will work. Prefer tox
# envs to system path. If there is more than one tox env, it doesn't
# matter which one we use, PATH will find the first command.
if [[ -d .tox ]] ; then
    for tox_bindir in $(find .tox -mindepth 2 -maxdepth 2 -name 'bin') ; do
        PATH=$(pwd)/$tox_bindir:$PATH
    done
fi

# Add all the nox envs to the path so that type will work. Prefer nox
# envs to tox and system path. If there is more than one nox env, it doesn't
# matter which one we use, PATH will find the first command.
if [[ -d .nox ]] ; then
    for nox_bindir in $(find .nox -mindepth 2 -maxdepth 2 -name 'bin') ; do
        PATH=$(pwd)/$nox_bindir:$PATH
    done
fi

for command in $commands; do
    # Use -P instead of -p because we always want a path here even if
    # there is an alias or builtin. We also filter blank lines as we
    # only want lines with paths and in some cases type seems to produce
    # blank lines.
    found=$(type -P $command | grep -v ^$)
    if [[ -n $found ]] ; then
        echo $found
        break
    fi
done

exit $rc