Skip to content

build: disable UT testing multiple node versions #23709

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 9, 2022

Conversation

alan-agius4
Copy link
Collaborator

@alan-agius4 alan-agius4 commented Aug 9, 2022

With this change we disable running UTs on multiple node.js versions. This is mainly an interim solution until we find the root cause of the memory increase and OOM errors during bazel test.

During this change I also noticed that the toolchain was configured incorrectly. Setting the toolchain to use Node.js 16 causes the App-shell tests to fail when used under Bazel. See: https://app.circleci.com/pipelines/github/angular/angular-cli/25009/workflows/4ea86ec8-d1f7-4c91-8810-76f10f8e878c/jobs/325982

@alan-agius4 alan-agius4 added the target: patch This PR is targeted for the next patch release label Aug 9, 2022
@alan-agius4 alan-agius4 force-pushed the bazel-node-js-multiple branch from a3d5864 to 1b2216f Compare August 9, 2022 09:43
@alan-agius4 alan-agius4 marked this pull request as ready for review August 9, 2022 09:43
With this change we disable running UTs on multiple node.js versions. This is mainly an interim solution until we find the root cause of the memory increase and OOM errors during bazel test.

During this change I also noticed that the toolchain was configured incorrectly. Setting the toolchain to use Node.js 16 causes the App-shell tests to fail when used under Bazel. See: https://app.circleci.com/pipelines/github/angular/angular-cli/25009/workflows/4ea86ec8-d1f7-4c91-8810-76f10f8e878c/jobs/325982
@alan-agius4 alan-agius4 force-pushed the bazel-node-js-multiple branch from 1b2216f to 59d0190 Compare August 9, 2022 10:53
@alan-agius4
Copy link
Collaborator Author

//cc @jbedard

@alan-agius4 alan-agius4 requested a review from clydin August 9, 2022 10:53
@alan-agius4 alan-agius4 added the action: review The PR is still awaiting reviews from at least one requested reviewer label Aug 9, 2022
@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Aug 9, 2022
@clydin clydin merged commit 167887d into angular:main Aug 9, 2022
@alan-agius4 alan-agius4 deleted the bazel-node-js-multiple branch August 9, 2022 17:48
@jbedard
Copy link
Contributor

jbedard commented Aug 10, 2022

FWIW this issue seems similar? nrwl/nx#10537

This is an option for now disabling the failing test and splitting the node 14 vs 16 into separate CI steps: #23714

@alan-agius4
Copy link
Collaborator Author

FWIW this issue seems similar? nrwl/nx#10537

It is similar, but the unlike the issue, the actually builder works when run outside of Bazel.

@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 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants