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] Run small-test #382

Open
guilhermejccavalcanti opened this issue Nov 29, 2024 · 16 comments
Open

[BUG] Run small-test #382

guilhermejccavalcanti opened this issue Nov 29, 2024 · 16 comments
Assignees

Comments

@guilhermejccavalcanti
Copy link

Hi!

I was trying to execute the setup, then I got the following error when running make small-test

image

Seems like this is a problem in plume-lib/merging build.gradle file:

image

@benedikt-schesch
Copy link
Owner

@mernst We fixed this right? I think it should be working now

@mernst
Copy link
Collaborator

mernst commented Jan 31, 2025

I will close the issue; if the problem recurs, please re-open.

@mernst mernst closed this as completed Jan 31, 2025
@guilhermejccavalcanti
Copy link
Author

guilhermejccavalcanti commented Feb 3, 2025

@benedikt-schesch thank you for the support. I was trying to run it again (command make small-test) after your feedback, but I got the same issue. So I realized that the setup is specifically pointing to the commit plume-lib/merging@6d81957 (which is outdated I presume) as you can see in the print below:

Image

So can you tell me where to change to point the setup to the most suitable commit of plume-lib/merging?

EDIT: @benedikt-schesch my bad, my version of benedikt-schesch/AST-Merging-Evaluation was outdated. I updated to 2a3e7f9 and seems like it is now running fine!

@benedikt-schesch
Copy link
Owner

Good to hear. Maybe we'll add a check for this

@guilhermejccavalcanti
Copy link
Author

guilhermejccavalcanti commented Feb 4, 2025

Hey @benedikt-schesch! After running the tests (make small-test), I got the following output. I do not know if it is correct. Could you please give a me clue? Thanks in advance.

Image

@benedikt-schesch
Copy link
Owner

Hey, so at the end it is saying that some columns are not equal and more specifically it is all the sporks columns so something seems to be off with spork but it also means that the rest is all working as it should which is very good. But it also looks like to me you are not ont the latest main branch because, could you pull and update to the latest version of the main branch? (If you did any manual changes please temporarily remove them). If you get an error again then feel free to post it here and I can look into it.

@guilhermejccavalcanti
Copy link
Author

guilhermejccavalcanti commented Feb 4, 2025

@benedikt-schesch I'm not using the latest version of the main branch because megiraf's pull request caused some dependency issues related to the Rust language used by their tool (I think they should have told the necessary dependencies...). Were you aware of this? Perhaps your PC already has the necessary dependencies... Here, I am building a docker image to facilitate the execution of the experiment,

I am using the version just before megiraf, namely: 2a3e7f9

@benedikt-schesch
Copy link
Owner

Ok so there is a problem with spork. I suspect it is not running properly on your machine and that it is simply reverting to git. Could you post the content of cache-small/sha_cache_entry/benedikt-schesch/logs/48199306f02a82abdeff0c01fab1ce112126d727_488122ce6c91e157d1f49b88b79feaa083fdee5b_spork.log
This should exist after you ran make small-test

@benedikt-schesch
Copy link
Owner

Very strange to be honest. Not really clear what is going wrong here. Could you checkout the branch spork_debugging, rerun make small-test and then send me the same file. On this branch I am capturing the spork logs and checking the java version. I am not sure why your spork is behaving a bit strangely

@benedikt-schesch
Copy link
Owner

Also what OS are you using? It seems like you don't have killall which is very useful and I strongly recommend to have it because spork has a tendency to escape and run forever

@guilhermejccavalcanti
Copy link
Author

Very strange to be honest. Not really clear what is going wrong here. Could you checkout the branch spork_debugging, rerun make small-test and then send me the same file. On this branch I am capturing the spork logs and checking the java version. I am not sure why your spork is behaving a bit strangely

Here is the new log
48199306f02a82abdeff0c01fab1ce112126d727_488122ce6c91e157d1f49b88b79feaa083fdee5b_spork.log

Also what OS are you using? It seems like you don't have killall which is very useful and I strongly recommend to have it because spork has a tendency to escape and run forever

I am using a docker container with ubuntu:22.04 configured with the dependencies described in your readme file, and others that are not in the readme, but I had to install (latex por instance) to make it work.

@benedikt-schesch
Copy link
Owner

Ok so your are having an internal error with Spork so it is reverting to git:

class spoon.reflect.factory.ModuleFactory$CtUnnamedModule cannot be cast to class spoon.reflect.declaration.CtType (spoon.reflect.factory.ModuleFactory$CtUnnamedModule and spoon.reflect.declaration.CtType are in unnamed module of loader 'app')
Spork encountered an error in structured merge. Falling back to line-based merge

I think it could be due to the use of java 21 that you are using:

java version "21.0.6" 2025-01-21 LTS
Java(TM) SE Runtime Environment Oracle GraalVM 21.0.6+8.1 (build 21.0.6+8-LTS-jvmci-23.1-b55)
Java HotSpot(TM) 64-Bit Server VM Oracle GraalVM 21.0.6+8.1 (build 21.0.6+8-LTS-jvmci-23.1-b55, mixed mode, sharing)

I use this one:

openjdk version "17.0.7" 2023-04-18 LTS
OpenJDK Runtime Environment Zulu17.42+21-CRaC-CA (build 17.0.7+7-LTS)
OpenJDK 64-Bit Server VM Zulu17.42+21-CRaC-CA (build 17.0.7+7-LTS, mixed mode, sharing)

Try to use Java 17 and/or try to use exactly the same one. For that change your JAVA_HOME path

@benedikt-schesch
Copy link
Owner

Also make sure to install killall

@benedikt-schesch benedikt-schesch changed the title [BUG] Unable to resolve dependency [BUG] Run small-test Feb 5, 2025
@guilhermejccavalcanti
Copy link
Author

Thanks @benedikt-schesch, I think killall and Java 17 did the trick.

This is the correct output, right?

Image

@benedikt-schesch
Copy link
Owner

Looks all good. I'll do a few changes to make sure this is no longer an issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants