wandb / client-ng

Experimental wandb CLI and Python API - See Experimental section below.
http://wandb.com
16 stars 7 forks source link

TPU utilization logging [WIP] #179

Open farizrahman4u opened 4 years ago

coveralls commented 4 years ago

Pull Request Test Coverage Report for Build 67ac9156-71ec-4dc8-bb08-dd5f6a532478


Changes Missing Coverage Covered Lines Changed/Added Lines %
wandb/internal/stats.py 1 11 9.09%
wandb/internal/tpu.py 15 55 27.27%
<!-- Total: 16 66 24.24% -->
Files with Coverage Reduction New Missed Lines %
wandb/apis/internal_runqueue.py 1 22.42%
wandb/filesync/dir_watcher.py 1 81.62%
wandb/internal/internal_api.py 1 61.36%
wandb/internal/meta.py 1 70.8%
wandb/internal/run.py 1 61.54%
wandb/internal/stats.py 1 14.18%
wandb/lib/ipython.py 1 80.0%
wandb/util.py 1 64.75%
tests/test_datastore.py 2 97.83%
tests/test_util.py 2 97.44%
<!-- Total: 110 -->
Totals Coverage Status
Change from base Build 789ef72f-b1a9-460c-8c97-3af7c02bd63f: 3.7%
Covered Lines: 13977
Relevant Lines: 21423

💛 - Coveralls
vanpelt commented 4 years ago

We should also look for the GCP zone and project environment variables. The ones I'm aware of:

CLOUDSDK_CORE_PROJECT CLOUDSDK_CORE_ZONE PROJECT_ID

The error message here explains to set tpu_zone, tpu_project but the user can't actually do that because they aren't instantiating the profiler. We should also give users a way to specify this via env or settings.