Skip to content

Repair frameworks not configured with a timeout #26

@jose

Description

@jose

Hi @tdurieux,

I have just noticed that some repair frameworks are configured with an explicit timeout and some are not.

  • Arja is correctly executed and configured. It is executed by the timeout command with the time limit defined in the config.py script.

  • Astor. Although the max_time value is hardcoded, it is the same as the one defined in the config.py script and Astor is properly configured with the -maxtime parameter. (Nevertheless, I would also use the timeout command, as you did for Arja, just in case Astor gets stuck at some point and it does not finish within the time limit)

  • NPEFix is configured with 100 iterations. As far I can see, by default, the timeout of each iteration is 5 seconds. Does this mean NPEFix only runs for a max time of 500 seconds?

  • Nopol is not executed by the timeout command and it does not seem to be properly configured. The parameter to configure Nopol's timeout is --maxTime "The maximum time execution in minute for the whole execution of Nopol. (default: 10)". However, the RepairThemAll framework does not set that parameter. Does this mean Nopol only runs for a max time of 10 minutes?

--
Best,
Jose

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions