Bug 2089996 - Unnecessary yarn install runs in e2e tests
Summary: Unnecessary yarn install runs in e2e tests
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Christoph Jerolimov
QA Contact: spathak@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2022-05-24 23:06 UTC by Christoph Jerolimov
Modified: 2022-08-10 11:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-08-10 11:14:04 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11517 0 None open Bug 2089996: Don't rerun yarn install when running tests 2022-05-24 23:07:11 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:14:15 UTC

Description Christoph Jerolimov 2022-05-24 23:06:35 UTC
Description of problem:
While running our e2e tests there are multiple `yarn install` runs that triggers also a `yarn generate`. Together each of this `yarn install` runs takes multiple minutes.

Version-Release number of selected component (if applicable):
4.10, 4.11, maybe earlier as well

How reproducible:
Always, but this affects only the CI build time

Steps to Reproduce:
Run a CI job.

Actual results:
Run multiple times the same yarn install scripts.

Expected results:
Should run yarn install just once, if possible.

Additional info:

Comment 2 Christoph Jerolimov 2022-06-03 07:40:03 UTC
Change doesn't affect the product. No doc update is needed. Mark it as verified.

Comment 4 errata-xmlrpc 2022-08-10 11:14:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.