Opentelemetry-js: coverage runs take 2 min out of every circleci build

Created on 4 Nov 2019  路  6Comments  路  Source: open-telemetry/opentelemetry-js

See https://circleci.com/gh/markwolff/opentelemetry-js/673 for instance -- the fact that each different JS version is repeating the same code coverage (6x) reports results in extensive queuing for the entire otel organization.

Can you consider only running full coverage reports on a subset of environments?

bug

Most helpful comment

Thank you! Your sister SIGs appreciate it.

All 6 comments

In Java we run coverage only for one version

I think it makes sense to remove code coverage from each different JS version and keep only two coverage report -> node (maybe node:11) and browser (node:12-browsers).

Also, somehow Install Dependencies job takes > 3m almost every time, need to do some investigation.

Per SIG, these are the action items:

  1. Merge lint and docs jobs.
  2. Only install doc and lint dependencies (not a full install) - full install takes > 3mins.
  3. Only run coverage on latest node and browser build
  4. Investigate current caching mechanism

Thank you! Your sister SIGs appreciate it.

Merge lint and docs jobs.

Done in #495

Only install doc and lint dependencies (not a full install) - full install takes > 3mins.

Done in #498

Only run coverage on latest node and browser build

Done in #496

Investigate current caching mechanism

Done in #514

Also, we have removed duplicate compile step(#510) and redundant test from types package (#511).

Feel free to reopen the issue if there's something that all of these doesn't solve.

Thanks a million!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rbruggem picture rbruggem  路  5Comments

giri-jeedigunta picture giri-jeedigunta  路  5Comments

naseemkullah picture naseemkullah  路  5Comments

naseemkullah picture naseemkullah  路  7Comments

naseemkullah picture naseemkullah  路  6Comments