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

[Bug]: java.lang.NoClassDefFoundError with dead code elimination #43564

Closed
MaryamZi opened this issue Nov 11, 2024 · 2 comments
Closed

[Bug]: java.lang.NoClassDefFoundError with dead code elimination #43564

MaryamZi opened this issue Nov 11, 2024 · 2 comments
Labels
Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. Type/Bug userCategory/Compilation

Comments

@MaryamZi
Copy link
Member

Description

$title, even when run with hardcoded types to skip.

Running Tests

	io

	testNonBlockingReadLine has failed.


		[fail] testNonBlockingReadLine:

		    error("java.lang.NoClassDefFoundError: ballerina/io/1/read")
				callableName: $lambda$_11 moduleName: ballerina.io$test.1.tests.console_io fileName: tests/console_io.bal lineNumber: 40

Steps to Reproduce

  1. Build the ballerina/io module (skipping tests) with lang timestamped version 2201.11.0-20241111-101700-af28a18f
  2. Navigate to the io module source and do a bal test with the intermediate pack created when building the io module (/target/ballerina-runtime/).

Affected Version(s)

No response

OS, DB, other environment details and versions

No response

Related area

-> Compilation

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

@ballerina-bot ballerina-bot added needTriage The issue has to be inspected and labeled manually userCategory/Compilation labels Nov 11, 2024
@MaryamZi MaryamZi added Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. and removed needTriage The issue has to be inspected and labeled manually labels Nov 11, 2024
@MaryamZi
Copy link
Member Author

Fixed by @Thushara-Piyasekara in #43566.

Thank you, @Thushara-Piyasekara :)

Copy link

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.

@MaryamZi MaryamZi added the Reason/EngineeringMistake The issue occurred due to a mistake made in the past. label Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Team/CompilerFE All issues related to Language implementation and Compiler, this exclude run times. Type/Bug userCategory/Compilation
Projects
None yet
Development

No branches or pull requests

2 participants