Increase console memory request

[spadgett]

The console build pods are getting out of memory killed. This is happening on almost every PR.

could not wait for build: the build console failed after 6m44s with reason OutOfMemoryKilled: The build pod was killed due to an out of memory condition.

Done in 271.62s.
yarn run v1.7.0
$ rm -rf ./public/dist && NODE_ENV=production ts-node -O '...:"commonjs"}' ./node_modules/.bin/webpack --mode=production
Starting type checking service...
Using 1 worker with 2048MB memory limit

/cc @stevekuznetsov @petr-muller

Let me know if you guys have concerns with this change or if there is a better way to fix it.

[spadgett]

@jcaianirh

[jcaianirh]

lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: jcaianirh, spadgett

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@spadgett: Updated the following 2 configmaps:

• ci-operator-configs configmap in namespace ci using the following files:
  • key openshift-console-master.yaml using file ci-operator/config/openshift/console/openshift-console-master.yaml
• ci-operator-configs configmap in namespace ci-stg using the following files:
  • key openshift-console-master.yaml using file ci-operator/config/openshift/console/openshift-console-master.yaml

Details

In response to this:

The console build pods are getting out of memory killed. This is happening on almost every PR.

could not wait for build: the build console failed after 6m44s with reason OutOfMemoryKilled: The build pod was killed due to an out of memory condition.

Done in 271.62s.
yarn run v1.7.0
$ rm -rf ./public/dist && NODE_ENV=production ts-node -O '...:"commonjs"}' ./node_modules/.bin/webpack --mode=production
Starting type checking service...
Using 1 worker with 2048MB memory limit

/cc @stevekuznetsov @petr-muller

Let me know if you guys have concerns with this change or if there is a better way to fix it.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[smarterclayton]

After this change I see you using 4.1GB. So it looks like you just slightly hit the limit incrementally.

[jcaianirh]

@smarterclayton are you suggesting we increment using a smaller value?

[spadgett]

Yeah, it's much better, although I still see occasional errors in console-e2e tests:

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_console/1173/pull-ci-openshift-console-master-console-e2e/382

ERROR in ./node_modules/lodash/lodash.js
Module build failed: Error: ENOMEM: not enough memory, read
 @ ./node_modules/patternfly-react/dist/esm/components/DualListSelector/DualListControlled.js 14:0-33 111:14-21
 @ ./node_modules/patternfly-react/dist/esm/components/DualListSelector/index.js
 @ ./node_modules/patternfly-react/dist/esm/index.js
 @ ./public/components/error.tsx
 @ ./public/components/app.jsx
 @ multi ./polyfills.js ./public/components/app.jsx

[smarterclayton]

No.