Skip to content
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

NODEJS tests are failing #113

Closed
leighmcculloch opened this issue Dec 18, 2024 · 2 comments
Closed

NODEJS tests are failing #113

leighmcculloch opened this issue Dec 18, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@leighmcculloch
Copy link
Member

What version are you using?

It's difficult to know, because the jobs that use it don't seem to really specify:
https://github.com/stellar/stellar-cli/actions/runs/12319954892/job/34577619594

But it's failing with the latest version as of today.

What did you do?

Run system tests.

What did you expect to see?

Success.

What did you see instead?

--- Failed steps:
  Scenario Outline: DApp developer compiles, deploys and invokes a contract # ./dapp_develop.feature:21
    And The result should be to receive 0 contract events and 1 diagnostic events for soroban-hello-world-contract from NODEJS # ./dapp_develop.feature:29
      Error: 
	Error Trace:	dapp_develop_test.go:230
	            				value.go:596
	            				value.go:380
	            				stepdef.go:182
	            				suite.go:183
	            				suite.go:391
	            				suite.go:447
	Error:      	Not equal: 
	            	expected: 1
	            	actual  : 2
	Messages:   	Expected 1 diagnostic events for soroban-hello-world-contract using NODEJS but got 2

cc @Shaptic

@leighmcculloch leighmcculloch added the bug Something isn't working label Dec 18, 2024
@leighmcculloch
Copy link
Member Author

Started to see failures on the CLI, even on commits that previously passed the system-test. The test failure seems to be NODEJS related, which I assume means the latest js-stellar-sdk has become incompatible with it.

@sreuland
Copy link
Contributor

Yes, newer version of the js sdk had changed exported pkg names which the test js client scripts in here were importing, this was fixed on #114, that is likely the resolution for this ticket, and can close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants