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

Update machine image for GPU CI #1084

Merged
merged 9 commits into from
Aug 1, 2023
Merged

Update machine image for GPU CI #1084

merged 9 commits into from
Aug 1, 2023

Conversation

ivirshup
Copy link
Member

  • Closes #
  • Tests added
  • Release note added (or unnecessary)

Trying a new AMI for GPU CI

@codecov
Copy link

codecov bot commented Jul 31, 2023

Codecov Report

Merging #1084 (8eaf5f0) into main (778cf37) will increase coverage by 0.01%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1084      +/-   ##
==========================================
+ Coverage   84.66%   84.68%   +0.01%     
==========================================
  Files          35       35              
  Lines        5112     5112              
==========================================
+ Hits         4328     4329       +1     
+ Misses        784      783       -1     
Flag Coverage Δ
gpu-tests 52.32% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

@ivirshup
Copy link
Member Author

Currently creating an AMI based on the instructions laid out here:

Initially had tried defining a docker file, but it turns out there are complications here about talking to a GPU and it wasn't clear these would be resolved in the setup used by amazons image tutorial.

It may be worth looking into the EC2 image builder for creating our images in the future: https://aws.amazon.com/image-builder/. I think it would allow automating the building of images so we can keep the base image up to date.

.cirun.yml Outdated
@@ -2,7 +2,7 @@ runners:
- name: aws-gpu-runner
cloud: aws
instance_type: g4dn.xlarge
machine_image: ami-0678adbdcb4c3a662
machine_image: ami-0139a05e194cbd9a0
Copy link
Contributor

Choose a reason for hiding this comment

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

Note: This failed here: https://github.com/scverse/anndata/pull/1084/checks?check_run_id=15487580477
Is this AMI in eu-west-1 (that's default region)? If not, then you need to add region: <region-name> in here.

Copy link
Member Author

Choose a reason for hiding this comment

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

I believe this didn't work because I didn't wait for the AMI to build to stop the instance, so the AMI failed to build.

Copy link
Member Author

Choose a reason for hiding this comment

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

How would I tell what region it's associated with? I added eu-north-1 for the new one, but it's not super clear from the UI

Copy link
Contributor

Choose a reason for hiding this comment

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

It's visible on the top right in the aws console, you already got it anyway. :)

@ivirshup ivirshup added this to the 0.10.0 milestone Aug 1, 2023
@ivirshup ivirshup merged commit 375a96f into main Aug 1, 2023
10 checks passed
@ivirshup ivirshup deleted the update-ami branch August 1, 2023 14:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants