André Silva

> When using the pipeline in pure Java, it should fail if we make sure to use the JVM 14. Which JVM do you use in your experiment? I used...

> That's an excellent idea. Would you create an issue to keep track of it? Yes, see #1132 . > Do you mean Repairnator itself doesn't compile? If yes, this...

This is due to Maven blocking `external HTTP insecure URLs (...) by default` since `3.8.1`. See https://maven.apache.org/docs/3.8.1/release-notes.html You can also overcome this issue by disabling this (see https://stackoverflow.com/questions/67001968/how-to-disable-maven-blocking-external-http-repositores).

1. `GithubAPIPullRequestAdapter` based on `GithubAPICommitAdapter` but scans for pull requests that have new commits inside of the interval (since to until) 2. `GithubPullRequestScanner` based on `GithubScanner`, but that fetches pull...

For some reason, `Lapse`s don't have any `Decision`, resulting in `executions` not being populated with anything. I haven't yet been able to understand why this happens.

No, the issue comes from `npefix` and hasn't been fixed yet. See https://github.com/SpoonLabs/npefix/issues/24

We need to move all repair step logic to `repairnator-pipeline`. This is already the case for all repair tools except for NPEFix, where the logic is in `maven-repair`. This results...

This still happens from time to time, so I think it's better to keep it open.

Another flaky test identified: - https://github.com/eclipse/repairnator/blob/103e6415f012a58b4686a92c66b8d761f0f96253/src/repairnator-pipeline/src/test/java/fr/inria/spirals/repairnator/process/step/TestGatherTestInformation.java#L109 [Failed](https://ci.eclipse.org/repairnator/job/repairnator-ci/job/PR-1204/2/testReport/junit/fr.inria.spirals.repairnator.process.step/TestGatherTestInformation/testGatherTestInformationOnlyOneErroring/) and [Passed](https://ci.eclipse.org/repairnator/job/repairnator-ci/job/PR-1204/4/) Reason: sometimes the error message of the test project returns two lines without `\n` separating them

Yes, but before we need to release a new version of https://github.com/SpoonLabs/astor and a new version of repairnator. (see https://github.com/SpoonLabs/astor/issues/333)