Skip to content

Conversation

@jelbourn
Copy link
Member

@jelbourn jelbourn commented Sep 29, 2016

The :test:deps task included both :build:components:inline and :watch:components:spec. The latter use the CJS output (which we want for karma), but the former uses the ESM output (which we don't want). This led to a race condition where the tests only passed when the CJS output ended up being there when the tests started.

I also:

  • Made sure that watch mode isn't used on CI
  • Added a bunch of comments to the tasks

@jelbourn jelbourn added the in progress This issue is currently in progress label Sep 29, 2016
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 29, 2016
@jelbourn jelbourn changed the title WIP chore: fix CI flakiness by using correct build targets chore: fix CI flakiness caused by race condition Sep 29, 2016
@jelbourn jelbourn added pr: needs review and removed in progress This issue is currently in progress labels Sep 29, 2016
@jelbourn
Copy link
Member Author

R: @hansl

Copy link
Contributor

@hansl hansl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@jelbourn jelbourn merged commit 3045a05 into angular:master Sep 29, 2016
@jelbourn jelbourn deleted the ci-test-build-fix branch September 13, 2017 04:37
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla: yes PR author has agreed to Google's Contributor License Agreement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants