Fail to capture the failed testing details

[gouyang]

when a testing fail, it always gets:
DockerTestFail: Good: ['error_check_stdout', 'crash_check_stdout']; Not Good: ['error_check_stderr', 'crash_check_stderr']; Details: (error_check_stderr, No details); (crash_check_stderr, No details)

no details captured.

It looks like self.details in environment.py has no value assigned.

[cevich]

Could very well be, we'll check it out, thanks!

[cevich]

I am able to reproduce this, will investigate further...

[root@docker docker]# git reset --hard 0.5.5
HEAD is now at 833331b Docker: Release Update 0.5.5 (no API changes)
[root@docker docker]# ../../shared/version.py 
0.16.0-master-63-g35e93
[root@docker docker]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.0 (Maipo)
[root@docker docker]# rpm -q docker-io
docker-io-0.9.1-3.collider.el7.x86_64
[root@docker docker]# git am /tmp/63.patch 
Applying: subtests..run_twice: Add run container twice test Signed-off-by: Ouyang Guohua <gouyang@redhat.com>
[root@docker docker]# cd ../..
[root@docker client]# reset; tools/make_clean; ./autotest-local run docker --verbose --args=docker_cli/run_twice
...
09:32:44 DEBUG| DockerTestFail: Good: ['crash_check_stdout', 'error_check_stdout', 'usage_check_stdout', 'crash_check_stderr', 'usage_check_stderr']; Not Good: ['error_check_stderr']; Details: (error_check_stderr, No details)
...

[cevich]

Okay, I got a small patch that fixes this and will go into 0.6.1.