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

Missing line_numbers in Defects4J meta-data.json #73

Closed
thanhlecongg opened this issue May 8, 2023 · 3 comments
Closed

Missing line_numbers in Defects4J meta-data.json #73

thanhlecongg opened this issue May 8, 2023 · 3 comments

Comments

@thanhlecongg
Copy link
Contributor

Hi,
I recently observed that many data in meta-data.json has empty line numbers. I assume the line numbers are perfect fault localization which are necessary to run APR tools . I wonder if this is intentional and we should fill it later? Or you plan to integrate fault localization as a part of Cerberus. Many thanks.

@Marti2203
Copy link
Collaborator

Hi,
The lines which have information were taken from other tools (SequenceR mostly, this relates to issue #23 ). If somebody has information about the faulty lines, it would be nice to integrate it and yes, adding Fault Localization is on the roadmap.

@thanhlecongg
Copy link
Contributor Author

thanhlecongg commented Jun 1, 2023

Hi @Marti2203, I have extracted perfect fault localization for Defects4J. This could fix issue #23. The information could be found here.
https://drive.google.com/file/d/1xJslU2o9jv1t2TzPkf4tCjiO8nMgQ5HF/view?usp=sharing

The json file have the following structure:

{
"1": { // bug ID following your metadata files
        "subject": "Chart", // Defects4J subject
        "bug_id": 1, // Defects4J bug ID
        "locations": { 
            "org/jfree/chart/renderer/category/AbstractCategoryItemRenderer.java": [ // buggy methods
                1797
            ] // list of buggy lines
        }
    },
}

The information is extracted based on scripts provided by authors of Defects4J.

I planned to integrate it into your metadata files. However, I found that the current format in your meta data file does not support bugs with multiple classes so please help me to review and integrate it. Thanks.

@rshariffdeen
Copy link
Collaborator

Hi @thanhlecongg ,

thanks for looking into it, our current implementation needs some modification to handle multiple fault locations, once this is done we can seek your help to integrate the information for Defects4J.

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