Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Fix GPU CI on A4000 #1252

Merged
merged 8 commits into from
May 16, 2022
Merged

Conversation

benjaminhuth
Copy link
Member

Test if the ci job runs on the new a4000 GPU

Not intended to merge at the moment.

@benjaminhuth benjaminhuth added Infrastructure Changes to build tools, continous integration, ... 🚧 WIP Work-in-progress labels May 12, 2022
@benjaminhuth benjaminhuth added this to the WIP milestone May 12, 2022
@codecov
Copy link

codecov bot commented May 12, 2022

Codecov Report

Merging #1252 (4098e07) into main (df3e23d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1252   +/-   ##
=======================================
  Coverage   47.89%   47.89%           
=======================================
  Files         375      375           
  Lines       19588    19588           
  Branches     9214     9214           
=======================================
  Hits         9382     9382           
  Misses       3822     3822           
  Partials     6384     6384           

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

@asalzburger
Copy link
Contributor

RuntimeError: parallel_for failed: cudaErrorNoKernelImageForDevice: no kernel image is available for execution on the device

@krasznaa might be able to help here, I suppose ?

.gitlab-ci.yml Outdated Show resolved Hide resolved
@paulgessinger
Copy link
Member

FYI I removed the docker-gpu-nvidia tag from the new runner (but kept the docker-gpu-a4000 tag) to prevent the default CI to run on that machine.

@paulgessinger
Copy link
Member

Seems to have worked now.

.gitlab-ci.yml Outdated Show resolved Hide resolved
@paulgessinger paulgessinger changed the title ci: Test A4000 GPU with CI ci: Fix GPU CI on A4000 May 16, 2022
Copy link
Member

@paulgessinger paulgessinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@paulgessinger paulgessinger added automerge and removed 🚧 WIP Work-in-progress automerge labels May 16, 2022
@kodiakhq kodiakhq bot merged commit 190d85b into acts-project:main May 16, 2022
@benjaminhuth benjaminhuth deleted the ci/a4000-gpu branch May 16, 2022 08:36
@acts-project-service
Copy link
Collaborator

The backport to develop/v19.0.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-develop/v19.0.x develop/v19.0.x
# Navigate to the new working tree
cd .worktrees/backport-develop/v19.0.x
# Create a new branch
git switch --create backport-1252-to-develop/v19.0.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 190d85b5e4fde34d0bcc0bf1bf728ba6ca7722f6
# Push it to GitHub
git push --set-upstream origin backport-1252-to-develop/v19.0.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-develop/v19.0.x

Then, create a pull request where the base branch is develop/v19.0.x and the compare/head branch is backport-1252-to-develop/v19.0.x.

paulgessinger pushed a commit to paulgessinger/acts that referenced this pull request Sep 7, 2022
Test if the ci job runs on the new a4000 GPU

Not intended to merge at the moment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge backport develop/v19.0.x Infrastructure Changes to build tools, continous integration, ...
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants