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.

Sign up for GitHub

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

Jump to bottom

Cache name should not be longer than 64 chars #14461

Closed
dsouzai opened this issue Feb 8, 2022 · 0 comments · Fixed by adoptium/TKG#275
Closed

Cache name should not be longer than 64 chars #14461

dsouzai opened this issue Feb 8, 2022 · 0 comments · Fixed by adoptium/TKG#275
Labels
comp:test test failure

Comments

@dsouzai
Copy link
Contributor

dsouzai commented Feb 8, 2022

Failure link

Happens in PR build with sanity.functional+aot

Optional info

  • intermittent failure (yes|no): no
  • regression or new test: new

Failure output (captured from console output)

[2022-02-08T16:57:09.840Z] JVMSHRC061E Cache name should not be longer than 64 chars. Cache not created.
[2022-02-08T16:57:09.840Z] JVMJ9VM015W Initialization error for library j9shr29(11): JVMJ9VM009E J9VMDllMain failed
[2022-02-08T16:57:09.840Z] Error: Could not create the Java Virtual Machine.
[2022-02-08T16:57:09.840Z] Error: A fatal exception has occurred. Program will exit.

Happens in tests such as Jep397Tests_testSubClassOfSealedSuperFromDifferentPackageInSameUnamedModule_0 and Jep397Tests_testSubClassOfSealedSuperFromDifferentPackageInSameNamedModule_0
@dsouzai dsouzai mentioned this issue Feb 8, 2022
Open
8 tasks
dsouzai added a commit to dsouzai/TKG that referenced this issue Feb 9, 2022
@dsouzai
Use a specific name for SCC
e2d9fd6 
There are some tests [1] that fail because the SCC name is too large.
The SCC name when the aot test flag is set is derived from the test
name. In order to prevent this issue, simply use the same name for all
tests. This is ok because prior to and after running tests, all SCCs are
destroyed. Additionally, this does not impact any future ability to run
tests in parallel as this is already not possible; the fact that all
SCCs are destroyed between tests means that test could impact the
validity of another.

[1] eclipse-openj9/openj9#14461

Signed-off-by: Irwin D'Souza <[email protected]>
@dsouzai dsouzai mentioned this issue Feb 9, 2022
Merged
@dsouzai dsouzai mentioned this issue Feb 9, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
comp:test test failure
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use a specific name for SCC dsouzai/TKG
1 participant
@dsouzai