Removing langchain.js from testing suite due to yarn is necessary for installation

[pacostas]

Removing langchain.js from the testing suite.

This PR removes langchain.js from the testing suite because the yarn binary isn't available on the base images.

Until we further investigate how to properly include and install the yarn binary on the base images to test the langchain.js library, it's better to remove langchain.js. Currently, the failing test is a false alarm indication, as Langchain itself is not failing.

[phracek]

[test-upstream]

[github-actions]

Testing Farm results

name	compose	arch	status	started (UTC)	time	logs
Fedora - UpstreamTests - 22-minimal	Fedora-latest	x86_64	✅ passed	18.11.2025 08:04:29	5min 39s	test pipeline
Fedora - UpstreamTests - 24-minimal	Fedora-latest	x86_64	✅ passed	18.11.2025 08:04:28	5min 34s	test pipeline
Fedora - UpstreamTests - 20-minimal	Fedora-latest	x86_64	✅ passed	18.11.2025 08:04:41	5min 46s	test pipeline
CentOS Stream 10 - UpstreamTests - 22-minimal	CentOS-Stream-10	x86_64	✅ passed	18.11.2025 08:04:26	8min 46s	test pipeline
CentOS Stream 10 - UpstreamTests - 24-minimal	CentOS-Stream-10	x86_64	✅ passed	18.11.2025 08:04:37	8min 39s	test pipeline
RHEL8 - UpstreamTests - 20-minimal	RHEL-8.10.0-Nightly	x86_64	✅ passed	18.11.2025 08:04:34	15min 24s	test pipeline
RHEL10 - UpstreamTests - 22-minimal	RHEL-10-Nightly	x86_64	❌ error	18.11.2025 08:04:43	17min 20s	test pipeline
RHEL9 - UpstreamTests - 22-minimal	RHEL-9.6.0-Nightly	x86_64	✅ passed	18.11.2025 08:04:27	18min 41s	test pipeline
Fedora - UpstreamTests - 22	Fedora-latest	x86_64	✅ passed	18.11.2025 08:04:26	21min	test pipeline
RHEL9 - UpstreamTests - 20-minimal	RHEL-9.6.0-Nightly	x86_64	✅ passed	18.11.2025 08:04:28	20min 20s	test pipeline
Fedora - UpstreamTests - 24	Fedora-latest	x86_64	✅ passed	18.11.2025 08:04:32	21min 6s	test pipeline
RHEL10 - UpstreamTests - 24-minimal	RHEL-10-Nightly	x86_64	❌ error	18.11.2025 08:11:00	15min 54s	test pipeline
CentOS Stream 9 - UpstreamTests - 24	CentOS-Stream-9	x86_64	✅ passed	18.11.2025 08:04:29	23min 2s	test pipeline
CentOS Stream 9 - UpstreamTests - 20	CentOS-Stream-9	x86_64	❌ error	18.11.2025 08:04:28	23min 53s	test pipeline
RHEL8 - UpstreamTests - 22-minimal	RHEL-8.10.0-Nightly	x86_64	✅ passed	18.11.2025 08:15:00	12min 48s	test pipeline
CentOS Stream 10 - UpstreamTests - 24	CentOS-Stream-10	x86_64	✅ passed	18.11.2025 08:04:26	24min 13s	test pipeline
CentOS Stream 9 - UpstreamTests - 24-minimal	CentOS-Stream-9	x86_64	✅ passed	18.11.2025 08:20:58	9min 30s	test pipeline
CentOS Stream 9 - UpstreamTests - 20-minimal	CentOS-Stream-9	x86_64	✅ passed	18.11.2025 08:24:48	9min 53s	test pipeline
RHEL10 - UpstreamTests - 22	RHEL-10-Nightly	x86_64	❌ error	18.11.2025 08:04:29	31min 35s	test pipeline
RHEL8 - UpstreamTests - 22	RHEL-8.10.0-Nightly	x86_64	❌ error	18.11.2025 08:04:27	33min 11s	test pipeline
RHEL10 - UpstreamTests - 24	RHEL-10-Nightly	x86_64	❌ error	18.11.2025 08:04:27	32min 7s	test pipeline
Fedora - UpstreamTests - 20	Fedora-latest	x86_64	❌ error	18.11.2025 08:14:49	23min 8s	test pipeline
RHEL8 - UpstreamTests - 20	RHEL-8.10.0-Nightly	x86_64	❌ error	18.11.2025 08:10:56	29min 54s	test pipeline
RHEL9 - UpstreamTests - 24-minimal	RHEL-9.6.0-Nightly	x86_64	✅ passed	18.11.2025 08:23:06	17min 2s	test pipeline
RHEL9 - UpstreamTests - 24	RHEL-9.6.0-Nightly	x86_64	❌ error	18.11.2025 08:04:26	36min 40s	test pipeline
RHEL9 - UpstreamTests - 20	RHEL-9.6.0-Nightly	x86_64	✅ passed	18.11.2025 08:04:38	36min 22s	test pipeline
RHEL9 - UpstreamTests - 22	RHEL-9.6.0-Nightly	x86_64	❌ error	18.11.2025 08:10:49	34min 58s	test pipeline

[phracek]

Test failed for this reason for Version 20:

 [FAILED] for 'clients' test_client_fastify (00:05:43)
 [FAILED] for 'clients' test_client_pino (00:05:21)

for test_client_fastify:

> [email protected] test
> npm run lint && npm run unit && npm run test:typescript


> [email protected] lint
> npm run lint:eslint


> [email protected] lint:eslint
> eslint


> [email protected] unit
> borp

parsed config: test/**/*.test.js test/**/*.test.mjs
✔ should resolve immediately when reply[kReplyHijacked] is true (1.468486ms)
✖ should reject immediately when reply[kReplyHijacked] is true (0.511853ms)
  TypeError [Error]: t.plan is not a function
      at TestContext.<anonymous> (/opt/app-root/src/test/wrap-thenable.test.js:19:5)
      at Test.runInAsyncScope (node:async_hooks:206:9)
      at Test.run (node:internal/test_runner/test:631:25)
      at Test.processPendingSubtests (node:internal/test_runner/test:374:18)
      at Test.postRun (node:internal/test_runner/test:715:19)
      at Test.run (node:internal/test_runner/test:673:12)
      at async startSubtest (node:internal/test_runner/harness:216:3)

for pino

✔ destination (105.055102ms)
ℹ tests 516
ℹ suites 9
ℹ pass 514
ℹ fail 0
ℹ cancelled 2
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 193520.078485

✖ failing tests:

test at test/multistream.test.js:1:1
✖ /opt/app-root/src/test/multistream.test.js (60003.856481ms)
  'test timed out after 60000ms'

test at test/basic.test.js:1:1
✖ /opt/app-root/src/test/basic.test.js (60007.371521ms)
  'test timed out after 60000ms'
----------------------|---------|----------|---------|---------|------------------------------------
File                  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s                  
----------------------|---------|----------|---------|---------|------------------------------------
All files             |   97.44 |    97.09 |   98.44 |   97.44 |                                    
 src                  |   97.47 |     97.1 |   95.23 |   97.47 |                                    
  browser.js          |   96.23 |    96.93 |   94.59 |   96.23 | 124-125,367-368,375-378,490-500    
  file.js             |     100 |      100 |     100 |     100 |                                    
  pino.js             |     100 |    97.56 |     100 |     100 | 163                                
 src/lib              |   97.42 |    97.08 |     100 |   97.42 |                                    
  caller.js           |   86.66 |    66.66 |     100 |   86.66 | 14-15,23-24                        
  constants.js        |     100 |      100 |     100 |     100 |                                    
  levels.js           |   99.17 |    98.76 |     100 |   99.17 | 225-226                            
  meta.js             |     100 |      100 |     100 |     100 |                                    
  multistream.js      |   99.01 |    98.38 |     100 |   99.01 | 102-103                            
  proto.js            |   99.21 |    97.36 |     100 |   99.21 | 248-249                            
  redaction.js        |     100 |      100 |     100 |     100 |                                    
  symbols.js          |     100 |      100 |     100 |     100 |                                    
  time.js             |     100 |      100 |     100 |     100 |                                    
  tools.js            |   97.16 |    97.43 |     100 |   97.16 | ...122,275,302-303,306-310,343-344 
  transport-stream.js |   66.07 |    81.81 |     100 |   66.07 | 19-26,35-45                        
  transport.js        |    98.2 |       98 |     100 |    98.2 | 47-48,66                           
  worker.js           |   98.45 |     93.1 |     100 |   98.45 | 185-187                            
----------------------|---------|----------|---------|---------|------------------------------------
Test for image 'fedora/nodejs-20:20' FAILED (exit code: 1)
Test for image 'fedora/nodejs-20:20' FAILED (exit code: 1)

[phracek]

@pacostas Please address issues in this Pull request as well.

[pacostas]

@phracek I'm not able to reproduce that locally by using the following commands

cd ./s2i-nodejs-container
make build TARGET=rhel8 VERSIONS=20 BUILD_OPTIONS="-t rhel8_20_builder"
s2i build https://github.com/pinojs/pino.git rhel8_20_builder rhel8_20_pino -e NODE_ENV="development"
docker run -e INIT_WRAPPER=false -e NODE_CMD="npm run test" rhel8_20_pino 

Do you know if that is the closest environment that someone can have locally for testing the node modules?

[pacostas]

@phracek This issues are not related to the PR changes. Also fastify and pino do not fail on the nodejs upstream nightly builds. Can you please re-trigger the tests?