From 16eb6f1f3bfaa8bfde34abba762254a37a2de52b Mon Sep 17 00:00:00 2001
From: Ian Wienand <iwienand@redhat.com>
Date: Mon, 20 Nov 2017 17:50:08 +1100
Subject: [PATCH] Ignore missing .tox/env/logs directories for copy

Some tox users, such as dib-utils "tox -e functional" tests, don't
actually install a venv but just shell out to some commands.
Unfortunately, I'm not sure how to tell the difference between
intentionally missing logs like this, and what might be an
unintentional failure.  ignore_missing will allow this to run.

Change-Id: Iaa85a8326e746604966a9c1bb4cc85f44e92299b
---
 roles/fetch-tox-output/tasks/main.yaml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/roles/fetch-tox-output/tasks/main.yaml b/roles/fetch-tox-output/tasks/main.yaml
index a42f98b0f..ef317c19b 100644
--- a/roles/fetch-tox-output/tasks/main.yaml
+++ b/roles/fetch-tox-output/tasks/main.yaml
@@ -40,3 +40,6 @@
     rsync_opts:
       - "--ignore-missing-args"
   with_items: "{{ envlist }}"
+  # some tox runs may not create a virtualenv and thus have
+  # no ./tox/env directory
+  ignore_errors: yes