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

Compilation of bugs with multiple submodules #158

Open
jose opened this issue Dec 4, 2023 · 4 comments
Open

Compilation of bugs with multiple submodules #158

jose opened this issue Dec 4, 2023 · 4 comments

Comments

@jose
Copy link

jose commented Dec 4, 2023

Hi @nus-apr,

In the context of another project, I've noticed that all bugs in the Bugs.jar benchmark (except Commons-Math) are composed by multiple submodules. And I've also noticed that the root pom.xml of some bugs fail to compile but the true buggy submodule compiles successfully. Have you encountered such odd behaviour while compiling bugs with multiple submodules?

--
Best,
Jose

@Marti2203
Copy link
Collaborator

Hi @jose ,
Yes, I have also exhibited this in multiple projects in the VUL4J benchmark. In Cerberus, this can be tracked with a better benchmark driver and additional benchmark metadata to allow for more precise state tracking.

@jose
Copy link
Author

jose commented Dec 7, 2023

Thanks @Marti2203. Why don't we keep this issue open until the problem is formally addressed?

@Marti2203 Marti2203 reopened this Dec 7, 2023
@rshariffdeen
Copy link
Collaborator

Hi @jose
Thanks for opening the issue,
Indeed I have encountered this in other benchmarks as well, for such instances we change the scope the build to the buggy module. In our meta data file we specify the submodule which should be built and tested. This we achieve via creating our own scripts, which we were able to do so in our own versions of the benchmark.

We may be able to do the same for the bugs.jar as well. Will update this thread when we have updated the benchmark.

@jose
Copy link
Author

jose commented Dec 9, 2023

In our meta data file we specify the submodule which should be built and tested.

Ok.

Will update this thread when we have updated the benchmark.

Awesome, thanks.

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