-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
running two benchs leads to have nested directory structure for the logs #44
Comments
msimonin
added a commit
to msimonin/kolla-g5k
that referenced
this issue
Oct 7, 2016
msimonin
added a commit
to msimonin/kolla-g5k
that referenced
this issue
Oct 13, 2016
msimonin
added a commit
to msimonin/kolla-g5k
that referenced
this issue
Oct 13, 2016
rcherrueau
added a commit
that referenced
this issue
Oct 14, 2016
Augment results and workaround #44
rcherrueau
pushed a commit
to BeyondTheClouds/kolla-g5k-results
that referenced
this issue
Nov 3, 2016
Moved to : BeyondTheClouds/enos#7 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/BeyondTheClouds/kolla-g5k/blame/92e4ab657b860b32e7d0bf801e25c9626658ea51/ansible/roles/bench/tasks/logs.yml#L7
a second call, will create a
_data
subdirectory instead of copying the contents.As a result indexing the logs in the results vm will fail.
I suggest to
/tmp/kolla-logs
/var/lib/docker/volumes/kolla_logs/_data
insidesubsequent call should overwrite previous ones, which is a more desirable behaviour.
The text was updated successfully, but these errors were encountered: