Igor Minar 4237c34c78 test(ivy): mark failing test targets with fixme-ivy-jit and fixme-ivy-local tags (#26471) ... We are close enough to blacklist a few test targets, rather than whitelist targets to run... Because bazel rules can be composed of other rules that don't inherit tags automatically, I had to explicitly mark all of our ts_library and ng_module targes with "ivy-local" and "ivy-jit" tags so that we can create a query that excludes all fixme- tagged targets even if those targets are composed of other targets that don't inherit this tag. This is the updated overview of ivy related bazel tags: - ivy-only: target that builds or runs only under ivy - fixme-ivy-jit: target that doesn't yet build or run under ivy with --compile=jit - fixme-ivy-local: target that doesn't yet build or run under ivy with --compile=local - no-ivy-jit: target that is not intended to build or run under ivy with --compile=jit - no-ivy-local: target that is not intended to build or run under ivy with --compile=local PR Close #26471		2018-10-23 08:57:42 -07:00
..
example	build(bazel): use fine-grained npm deps (#26111) (#26488)	2018-10-19 20:59:29 -07:00
BUILD.bazel	test(ivy): mark failing test targets with fixme-ivy-jit and fixme-ivy-local tags (#26471)	2018-10-23 08:57:42 -07:00
common_package.spec.ts	build: update node type version (#25862)	2018-09-18 13:06:28 -07:00
core_package.spec.ts	build: update node type version (#25862)	2018-09-18 13:06:28 -07:00
example-custom-entry-point-name.golden	build(bazel): use ng_package entry_point_name for umd bundles (#23132)	2018-04-05 14:51:31 -07:00
example_package.golden	fix(bazel): don't produce ngfactory files for ng_packages (#23237)	2018-04-06 16:26:31 -07:00
example_package.spec.ts	build(bazel): use ng_package entry_point_name for umd bundles (#23132)	2018-04-05 14:51:31 -07:00