configs:
- config_name: python
data_files:
- split: test
path: data/python/*.json
🏟️ Long Code Arena (CI builds repair)
This is the benchmark for CI builds repair task as part of the 🏟️ Long Code Arena benchmark.
🛠️ Task. Given the logs of a failed GitHub Actions workflow and the corresponding repository snapshot, repair the repository contents in order to make the workflow pass.
All the data is collected from repositories published under permissive licenses (MIT, Apache-2.0, BSD-3-Clause, and BSD-2-Clause). The datapoints can be removed upon request.
To score your model on this dataset, you can use CI build repair benchmark. 📩 If you have any questions or requests concerning this dataset, please contact [email protected]
How-to
List all the available configs
via datasets.get_dataset_config_names
and choose an appropriate one.
Current configs: python
Load the data
via load_dataset:
from datasets import load_dataset
dataset = load_dataset("JetBrains-Research/lca-ci-builds-repair", split="test")
Note that all the data we have is considered to be in the test split.
NOTE: If you encounter any errors with loading the dataset on Windows, update the datasets library (was tested on datasets==2.16.1)
Usage
For the dataset usage please refer to our CI builds repair benchmark. Its workflow is following:
- Repairs repo by fix_repo_function function that utilizes repo state and logs of fails;
- Sends the datapoints to GitHub to run workflows;
- Requests results from GitHub;
- Analyzes results and prints them;
- Clones the necessary repos to the user's local machine.
The user should run their model to repair the failing CI workflows, and the benchmark will push commits to GitHub, returning the results of the workflow runs for all the datapoints.
Dataset Structure
This dataset contains logs of the failed GitHub Action workflows for some commits followed by the commit that passes the workflow successfully.
Note that, unlike other 🏟️ Long Code Arena datasets, this dataset does not contain repositories.
Datapoint Schema
Each example has the following fields:
| Field | Description |
|---|---|
contributor |
Username of the contributor that committed changes |
difficulty |
Difficulty of the problem (assessor-based. 1 means that the repair requires only the code formatting) |
diff |
Contents of the diff between the failed and the successful commits |
head_branch |
Name of the original branch that the commit was pushed at |
id |
Unique ID of the datapoint |
language |
Main language of the repository |
logs |
List of dicts with keys log (logs of the failed job, particular step) and step_name (name of the failed step of the job) |
repo_name |
Name of the original repository (second part of the owner/name on GitHub) |
repo owner |
Owner of the original repository (first part of the owner/name on GitHub) |
sha_fail |
SHA of the failed commit |
sha_success |
SHA of the successful commit |
workflow |
Contents of the workflow file |
workflow_filename |
The name of the workflow file (without directories) |
workflow_name |
The name of the workflow |
workflow_path |
The full path to the workflow file |
changed_files |
List of files changed in diff |
commit_link |
URL to commit corresponding to failed job |
Datapoint Example
{'contributor': 'Gallaecio',
'diff': 'diff --git a/scrapy/crawler.py b/scrapy/crawler.py/n<...>',
'difficulty': '2',
'head_branch': 'component-getters',
'id': 18,
'language': 'Python',
'logs': [{'log': '##[group]Run pip install -U tox\n<...>',
'step_name': 'checks (3.12, pylint)/4_Run check.txt'}],
'repo_name': 'scrapy',
'repo_owner': 'scrapy',
'sha_fail': '0f71221cf9875ed8ef3400e1008408e79b6691e6',
'sha_success': 'c1ba9ccdf916b89d875628ba143dc5c9f6977430',
'workflow': 'name: Checks\non: [push, pull_request]\n\n<...>',
'workflow_filename': 'checks.yml',
'workflow_name': 'Checks',
'workflow_path': '.github/workflows/checks.yml',
'changed_files': ["scrapy/crawler.py"],
'commit_link': "https://github.com/scrapy/scrapy/tree/0f71221cf9875ed8ef3400e1008408e79b6691e6"}