[Test]Make yatai service integration test less flaky

[yubozhao]

Description

Skip the Postgres + local storage yatai service integration for now, because it is very flaky with Github Action CI

Motivation and Context

How Has This Been Tested?

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature and improvements (non-breaking change which adds/improves functionality)
• Bug fix (non-breaking change which fixes an issue)
• Code Refactoring (internal change which is not user facing)
• Documentation
• Test, CI, or build

Component(s) if applicable

• BentoService (service definition, dependency management, API input/output adapters)
• Model Artifact (model serialization, multi-framework support)
• Model Server (mico-batching, dockerisation, logging, OpenAPI, instruments)
• YataiService gRPC server (model registry, cloud deployment automation)
• YataiService web server (nodejs HTTP server and web UI)
• Internal (BentoML's own configuration, logging, utility, exception handling)
• BentoML CLI

Checklist:

• My code follows the bentoml code style, both ./dev/format.sh and
  ./dev/lint.sh script have passed
  (instructions).
• My change reduces project test coverage and requires unit tests to be added
• I have added unit tests covering my code change
• My change requires a change to the documentation
• I have updated the documentation accordingly

[codecov]

Codecov Report

Merging #1298 (281c199) into master (ba0b9eb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1298   +/-   ##
=======================================
  Coverage   66.34%   66.34%           
=======================================
  Files         144      144           
  Lines        9329     9329           
=======================================
  Hits         6189     6189           
  Misses       3140     3140           

---

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 ba0b9eb...281c199. Read the comment docs.

[pep8speaks]

Hello @yubozhao, Thanks for updating this PR.

There are currently no PEP 8 issues detected in this PR. Cheers! 🍻

Comment last updated at 2020-12-04 01:02:41 UTC