MétaCan
Menu
Back to cohort
Record W4413216650 · doi:10.1145/3712255.3726730

Learning to Predict Code Review Rounds in Modern Code Review Using Multi-Objective Genetic Programming

2025· article· en· W4413216650 on OpenAlex
Moataz Chouchen, Issam Oukhay, Ali Ouni

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueProceedings of the Genetic and Evolutionary Computation Conference Companion · 2025
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsÉcole de Technologie SupérieureConcordia University
Fundersnot available
KeywordsComputer scienceGenetic programmingProgramming languageCode (set theory)Code reviewArtificial intelligenceStatic program analysisSoftware developmentSoftware

Abstract

fetched live from OpenAlex

Code review is an essential practice for software quality assurance. However, code review can be cumbersome as patches often undergo multiple rounds to fix bugs, enforce coding standards, and improve structure before merging or abandonment. Predicting the number of review rounds can help developers prioritize tasks and streamline the process. Existing machine learning models for review round prediction suffer from key limitations. Their black-box nature makes them difficult to interpret, reducing trust and adoption. Additionally, they rely on data re-balancing techniques that introduce artificial points, causing concept shifts and reducing reliability. To address these issues, we propose MORRP, a novel Multi-Objective Review Rounds Prediction approach. MORRP is based on Multi-Objective Genetic Programming (MOGP) to predict review rounds. Our method evolves interpretable models while optimizing precision, recall, and specificity without relying on data re-balancing. We evaluate our approach on three large open-source projects: Eclipse, OpenDaylight, and OpenStack. Results show that MORRP achieves competitive performance, with a micro F1 score between 0.65 and 0.75, outperforming complex ML models like Random Forest and LightGBM.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.629
Threshold uncertainty score0.767

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.035
GPT teacher head0.305
Teacher spread0.270 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it