Fix broken tests for release 0.25.0

[uilianries]

Release branch is fragile, only specific tests are able to run, or even CPT behavior could change during the tests.

Since release/* is a pattern for stable branch, many tests will fail when the channel is no specific the and CI manager is not mocked. Otherwise, CPT will recognize the current branch as stable and will change all package channel names during the tests.

About the package with the "name" only. It was because we use ConanAPIMock, and it only returns the package name, which represents conan_api.create returns. A typical return is:

{'recipe': {'id': 'foo/0.1@uilianries/testing', 'downloaded': False, 'exported': True, 'error': None, 'remote': None, 'time': datetime.datetime(2019, 3, 28, 19, 34, 35, 868478), 'dependency': False, 'name': 'foo', 'version': '0.1', 'user': 'uilianries', 'channel': 'testing'}, 'packages': [{'id': 'b6c337ae40a7acc0472113db7b56e3585b936000', 'downloaded': False, 'exported': False, 'error': None, 'remote': None, 'time': datetime.datetime(2019, 3, 28, 19, 34, 38, 524986), 'built': True, 'cpp_info': {'includedirs': ['include'], 'libdirs': ['lib'], 'resdirs': ['res'], 'bindirs': ['bin'], 'builddirs': [''], 'libs': ['hello'], 'rootpath': '/home/uilian/.conan/data/foo/0.1/uilianries/testing/package/b6c337ae40a7acc0472113db7b56e3585b936000', 'version': '0.1', 'description': '<Description of Foo here>', 'filter_empty': True}}]}

But since we don't to use all those fields, I only updated the reference and built.

Changelog: Omit

• Refer to the issue that supports this Pull Request.
• If the issue has missing info, explain the purpose/use case/pain/need that covers this Pull Request.
• I've read the Contributing guide.
• I've followed the PEP8 style guides for Python code.

[uilianries]

Docker tests are exotic, they require a Bintray login and only run when it's a stable branch. The latest commit changes this behavior, the idea is run a conan_server and remove all external dependencies (bintray, pypi, ...)

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (release/0.25.0@0af8d9c). Click here to learn what that means.
The diff coverage is 100%.

@@                Coverage Diff                @@
##             release/0.25.0     #365   +/-   ##
=================================================
  Coverage                  ?   92.45%           
=================================================
  Files                     ?       32           
  Lines                     ?     3010           
  Branches                  ?        0           
=================================================
  Hits                      ?     2783           
  Misses                    ?      227           
  Partials                  ?        0

Impacted Files	Coverage Δ
cpt/test/integration/base.py	100% <ø> (ø)
cpt/test/integration/docker_test.py	86.84% <100%> (ø)
cpt/packager.py	86.86% <100%> (ø)
cpt/test/unit/utils.py	96.42% <100%> (ø)
cpt/runner.py	90.81% <100%> (ø)
cpt/test/test_client/upload_checks_test.py	100% <100%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0af8d9c...a3b8074. Read the comment docs.

[uilianries]

All green again! 💚

[uilianries]

the good, the bad, and the time.sleep

[lasote]

I'm not sure about the docker test. But I'm merging and trying in the release branch. Thanks for the effort!

[uilianries]

I'm not sure about the docker test

It will increase more time in our CI time, but I don't like to discover an error only when the release branch is created.