-
Notifications
You must be signed in to change notification settings - Fork 124
Compile cpu #48
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
Compile cpu #48
Conversation
We have some issue to match the remote cache here:
|
As you seems not interested in #47 this is just the compile job in your published image on DockerHUb. |
This is something we can revisit later (Q1+) once the needs for internal CI have been covered. |
Ok but I don't know if the problem is at the CI level. it would be nice if you could compare the execution log with two builds on exactly same commit on the CI. I've tried on the nightly commit and the level of cache misses is different in every nightly release: https://discuss.tensorflow.org/t/adopting-open-source-dockerfiles-for-official-tf-nightly-ci/6050/17 |
/cc @theadactyl |
As we have recently removed this file from the repository I have refactored this in TF with tensorflow/tensorflow#57630 |
This is trying to figure out/monitor how much time, a build with the remote cache, requires on the standard Github Action hardware resources.