This repository has been archived by the owner on May 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 70
increase unit test coverage on main.go #396
Labels
Comments
Hi @sboeuf - any update on this? |
I am gonna look into this. |
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Sep 1, 2017
Add new tests to raise the unit-test coverage of main.go above 0%. Fixes clearcontainers#396. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
As @sboeuf is out and after a discussion, I'll look at this one. |
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Sep 1, 2017
Add new tests to raise the unit-test coverage of main.go above 0%. Fixes clearcontainers#396. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Sep 1, 2017
Add new tests to raise the unit-test coverage of main.go above 0%. Fixes clearcontainers#396. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Sep 4, 2017
Add new tests to raise the unit-test coverage of main.go above 0%. Fixes clearcontainers#396. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Sep 4, 2017
Add new tests to raise the unit-test coverage of main.go above 0%. Fixes clearcontainers#396. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Sep 4, 2017
Add new tests to raise the unit-test coverage of main.go above 0%. Fixes clearcontainers#396. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Sep 4, 2017
Add new tests to raise the unit-test coverage of main.go above 0%. Fixes clearcontainers#396. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
This one could be tricky.
Currently at 0%.
See #93.
The text was updated successfully, but these errors were encountered: