For a small issue, you may just want to email

For a merge request or for contributing in a specific branch, you need to have access on Inria members can login directly with their Inria login in the iLDAP tab on this page. External users need to request an external account from an Inria member (email When the account is created, you can login at the Standard tab on this page.

Submit an issue

You can create a new issue on this page. Please give as many details as possible (feature, fix, …), possibly a patch. We will either directly fix the issue in the master branch, or create a dedicated branch for you to work on, and eventually perform a merge request.

StarPU also has a repository on github, you can also submit issues on this page.

Contributing through a merge request

Create a fork

First you need to fork the repository into your own account by clicking on

Then, clone the repository on your laptop:

git clone

Once this is done, you can setup the StarPU repository as the upstream of your clone to simplify the update of your fork repository.

git remote add upstream

Note: If you do not have an Inria gitlab account, you can fork from the github mirror at, clone and add as upstream.

To update your fork with the upstream StarPU’s state:

git pull upstream master
git push -u origin master

Create a /Feature/ branch in your fork. To add a new feature, fix a bug, and so on, you need to create a new branch from the last state of the master branch.

git branch feature
git checkout feature

Apply your modifications in that /Feature/ branch. Then, you need to push this branch on your online repository.

git push origin feature

Merge request

Once your branch is online, on the gitlab or github interface, go to the repository/branches webpage, click on the merge request button next to your branch.

If the pull request is made to fix an issue, please name the branch issueXX, so it is automatically linked to the issue. In addition, please add fix issue #xx in the comment of the merge request to automatically close the issue when the PR is merged.

Before merging your branch, you will probably need to rebase the master onto it. To do that, just go at the HEAD of your /Feature/ branch and rebase:

git checkout feature
git rebase master

Then force to push on your origin

git push --force origin feature

Configure a runner to test your branch

To be effectively merged, your branch must be tested through the gitlab-ci mechanism.

To execute the tests, you should define a gitlab runner, running either on your laptop or any other remote machine. StarPU provides a Docker image whose recipe is defined at This project shows a minimal running this docker image to test StarPU.

To register a compatible runner, the requirements on the system are :

sudo apt-get update && sudo apt-get install -y curl
curl -fsSL | sudo apt-key add -
sudo apt install -y software-properties-common
sudo add-apt-repository "deb [arch=amd64] $(lsb_release -cs) stable"
sudo apt-get update
sudo apt install -y docker-ce
sudo usermod -aG docker ${USER}
newgrp docker

Example of registering sequence:

sudo gitlab-runner register
Please enter the gitlab-ci coordinator URL (e.g.
Please enter the gitlab-ci token for this runner:
# copy/paste the project's secret token here
# Setup the URL and the token found in the gitlab web interface (Settings -> CI/CD -> Runners -> Specific runners -> Set up a specific runner manually).
Please enter the gitlab-ci description for this runner:
Please enter the gitlab-ci tags for this runner (comma separated):
linux, ubuntu
Whether to run untagged builds [true/false]:
[false]: true
Whether to lock Runner to current project [true/false]:
Registering runner... succeeded                     runner=4jknGvoz
Please enter the executor: shell, ssh, docker+machine, docker-ssh+machine, kubernetes, docker, parallels, virtualbox, docker-ssh:
Please enter the default Docker image (e.g. ruby:2.1):
Runner registered successfully. Feel free to start it, but if it's running already the config should be automatically reloaded!