This is the fix you need https://github.com/linkedin/datahub/pull/3211

Thank you @high-hospital-85984 Now it raises another exception 😕

* What went wrong:
Execution failed for task ':datahub-web-react:yarnTest'.

I'm using

Java 8

and yarn

1.22.0

. Do you have any idea of what it can be?

Different things seem to be failing depending on the execution...I'm confused O.o

Task :metadata-io:test FAILED

com.linkedin.metadata.graph.ElasticSearchGraphServiceTest.setup FAILED
    org.testcontainers.containers.ContainerLaunchException at ElasticSearchGraphServiceTest.java:43
        Caused by: org.rnorth.ducttape.RetryCountExceededException at ElasticSearchGraphServiceTest.java:43
            Caused by: org.testcontainers.containers.ContainerLaunchException at ElasticSearchGraphServiceTest.java:43
                Caused by: org.testcontainers.containers.ContainerLaunchException at ElasticSearchGraphServiceTest.java:43

Another one:

> Task :metadata-ingestion:lint FAILED

return client

     def get_workunits(self) -> Iterable[MetadataWorkUnit]:
         client = self._get_looker_client()
         dashboards = client.all_dashboards(fields="id")
-        deleted_dashboards = client.search_dashboards(fields="id", deleted="true") if self.source_config.include_deleted else []
+        deleted_dashboards = (
+            client.search_dashboards(fields="id", deleted="true")
+            if self.source_config.include_deleted
+            else []
+        )
         dashboard_ids = [
             dashboard_base.id
             for dashboard_base in dashboards + deleted_dashboards
             if dashboard_base.id is not None
         ]
@@ -410,11 +414,17 @@
             self.reporter.report_dashboards_scanned()
             if not self.source_config.dashboard_pattern.allowed(dashboard_id):
                 self.reporter.report_dashboards_dropped(dashboard_id)
                 continue
             try:
-                fields = ["id", "title", "dashboard_elements", "dashboard_filters", "deleted"]
+                fields = [
+                    "id",
+                    "title",
+                    "dashboard_elements",
+                    "dashboard_filters",
+                    "deleted",
+                ]
                 dashboard_object = client.dashboard(
                     dashboard_id=dashboard_id, fields=",".join(fields)
                 )
             except SDKError:
                 # A looker dashboard could be deleted in between the list and the get
would reformat src/datahub/ingestion/source/looker.py

Oh no! 💥 💔 💥 1 file would be reformatted, 215 files would be left unchanged.

@green-football-43791 sorry for the trouble, but can you please advise?

yarn test

?

Test Suites: 31 passed, 31 total

Tests:       81 passed, 81 total

Snapshots:   0 total

Time:        46.54 s, estimated 96 s

Ran all test suites.

that is also likely the issue with

:metadata-io:test

I have noticed the ElasticSearchGraphServiceTest fails if run without sufficient resources

the

:metadata-ingestion:lint

looks real though... let me look into that

Thank you for your time @green-football-43791 🙏

I see the lint issue too- looks like this was a regression in master!

not sure how this snuck through CI 😕

let me fix this

Here's a PR to fix the lint issue:

Good and bad news @green-football-43791. Good: No more lint errors 🙂

Test Suites: 1 failed, 30 passed, 31 total

Tests:       2 failed, 79 passed, 81 total

Snapshots:   0 total

Time:        161.628 s

Bad: The timeouts issues remain 🙃

Summary of all failing tests
FAIL src/app/search/__tests__/SearchPage.test.tsx (72.202 s)
  ● SearchPage › renders loading

    thrown: "Exceeded timeout of 5000 ms for a test.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      11 |
      12 | describe('SearchPage', () => {
    > 13 |     it('renders loading', async () => {
         |     ^
      14 |         const promise = Promise.resolve();
      15 |         const { getByText } = render(
      16 |             <MockedProvider mocks={mocks} addTypename={false}>

      at src/app/search/__tests__/SearchPage.test.tsx:13:5
      at Object.<anonymous> (src/app/search/__tests__/SearchPage.test.tsx:12:1)

  ● SearchPage › renders multiple checked filters at once

    thrown: "Exceeded timeout of 5000 ms for a test.
    Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

      53 |     });
      54 |
    > 55 |     it('renders multiple checked filters at once', async () => {
         |     ^
      56 |         const promise = Promise.resolve();
      57 |         const { getByTestId, queryByTestId } = render(
      58 |             <MockedProvider mocks={mocks} addTypename={false}>

      at src/app/search/__tests__/SearchPage.test.tsx:55:5
      at Object.<anonymous> (src/app/search/__tests__/SearchPage.test.tsx:12:1)

Are you aware of something that can be done or should I only try to assess the possibility of developing in another machine? Nevertheless, maybe the requirements information should be updated. What do you think? Thank you again for your time and the quick fix. You rock!! 🚀

you can run

./gradlew build -x yarnTest -x test

that will skip the tests during build

Again, I can't thank you enough 🙂

Glad it worked 🎉

Separately, I'll look into removing these memory intensive tests from the main build