[CI] Move CPU-only jobs to xenial #24506
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) This will give us diff signal for CPU-only builds with FBGEMM enabled, ensuring quantization gets timely signal
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) This will give us diff signal for CPU-only builds with FBGEMM enabled, ensuring quantization gets timely signal
ezyang
previously approved these changes
Aug 16, 2019
|
@ezyang FYI this still doesn't build with FBGEMM ostensibly due to a binutils version mismatch in 14.04. I think i'm just going to enable a Xenial CPU configuration instead |
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) This will give us diff signal for CPU-only builds with FBGEMM enabled, ensuring quantization gets timely signal
jamesr66a
changed the title
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) This will give us diff signal for CPU-only builds with FBGEMM enabled, ensuring quantization gets timely signal
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) This will give us diff signal for CPU-only builds with FBGEMM enabled, ensuring quantization gets timely signal
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) This will give us diff signal for CPU-only builds with FBGEMM enabled, ensuring quantization gets timely signal
jamesr66a
changed the title
jamesr66a
changed the title
|
Currently getting this error in the regen script: |
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) This will give us diff signal for CPU-only builds with FBGEMM enabled, ensuring quantization gets timely signal
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) This will give us diff signal for CPU-only builds with FBGEMM enabled, ensuring quantization gets timely signal Built on top of #24795 (thanks @kostmo!)
|
I updated the ECRs for the renaming to remove gcc7.3 to gcc7 |
|
@kostmo on the regen script |
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) Trusty is out of standard support, and a mismatch in the binutils version causes FBGEMM to not build in pytorch even with a compiler that supports AVX512. This makes it so we build all that stuff in the CPU CI jobs (and otherwise brings us into <current year>-3 instead of <current year>-5) Built on top of #24795 (thanks @kostmo!)
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) Trusty is out of standard support, and a mismatch in the binutils version causes FBGEMM to not build in pytorch even with a compiler that supports AVX512. This makes it so we build all that stuff in the CPU CI jobs (and otherwise brings us into <current year>-3 instead of <current year>-5) Built on top of #24795 (thanks @kostmo!)
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) Trusty is out of standard support, and a mismatch in the binutils version causes FBGEMM to not build in pytorch even with a compiler that supports AVX512. This makes it so we build all that stuff in the CPU CI jobs (and otherwise brings us into <current year>-3 instead of <current year>-5) Built on top of #24795 (thanks @kostmo!)
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) Trusty is out of standard support, and a mismatch in the binutils version causes FBGEMM to not build in pytorch even with a compiler that supports AVX512. This makes it so we build all that stuff in the CPU CI jobs (and otherwise brings us into <current year>-3 instead of <current year>-5) Built on top of #24795 (thanks @kostmo!)
ezyang
approved these changes
Aug 21, 2019
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) Trusty is out of standard support, and a mismatch in the binutils version causes FBGEMM to not build in pytorch even with a compiler that supports AVX512. This makes it so we build all that stuff in the CPU CI jobs (and otherwise brings us into <current year>-3 instead of <current year>-5) Built on top of #24795 (thanks @kostmo!)
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) Trusty is out of standard support, and a mismatch in the binutils version causes FBGEMM to not build in pytorch even with a compiler that supports AVX512. This makes it so we build all that stuff in the CPU CI jobs (and otherwise brings us into <current year>-3 instead of <current year>-5) Built on top of #24795 (thanks @kostmo!)
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) Trusty is out of standard support, and a mismatch in the binutils version causes FBGEMM to not build in pytorch even with a compiler that supports AVX512. This makes it so we build all that stuff in the CPU CI jobs (and otherwise brings us into <current year>-3 instead of <current year>-5) Built on top of #24795 (thanks @kostmo!)
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) Trusty is out of standard support, and a mismatch in the binutils version causes FBGEMM to not build in pytorch even with a compiler that supports AVX512. This makes it so we build all that stuff in the CPU CI jobs (and otherwise brings us into <current year>-3 instead of <current year>-5) Built on top of #24795 (thanks @kostmo!)
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) Trusty is out of standard support, and a mismatch in the binutils version causes FBGEMM to not build in pytorch even with a compiler that supports AVX512. This makes it so we build all that stuff in the CPU CI jobs (and otherwise brings us into <current year>-3 instead of <current year>-5) Built on top of #24795 (thanks @kostmo!)
|
@pytorchbot retest this please |
Differential Revision: [D16862005](https://our.internmc.facebook.com/intern/diff/D16862005) Trusty is out of standard support, and a mismatch in the binutils version causes FBGEMM to not build in pytorch even with a compiler that supports AVX512. This makes it so we build all that stuff in the CPU CI jobs (and otherwise brings us into <current year>-3 instead of <current year>-5) Built on top of #24795 (thanks @kostmo!)
|
@jamesr66a merged this pull request in 4966268. |
|
This Docker version upgrade did NOT update https://github.com/pytorch/ossci-job-dsl/blob/master/src/main/groovy/ossci/pytorch/DockerVersion.groovy . When you fail to update this file, the new stable Docker image will get deleted after it becomes two weeks old. Please update this file! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stack from ghstack:
Differential Revision: D16862005
Trusty is out of standard support, and a mismatch in the binutils version causes FBGEMM to not build in pytorch even with a compiler that supports AVX512. This makes it so we build all that stuff in the CPU CI jobs (and otherwise brings us into -3 instead of -5)
Built on top of #24795 (thanks @kostmo!)