tensorflow / tensorflow/models

Broken imagenet script in slim

Open
#9,539 0 comments 0 reactions 2 assignees View on GitHub

@marksandler2 is already working on this.

Since Dec 8, 2020.

models:research type:bug
Dominant language
Python
Stars
77.7k
Forks
44.8k
PR merge metrics
No merged PRs in 30d

Description

Prerequisites

Please answer the following questions for yourself before submitting an issue.

  • I am using the latest TensorFlow Model Garden release and TensorFlow 2.
  • I am reporting the issue to the correct repository. (Model Garden official or research directory)
  • I checked to make sure that this issue has not already been filed.

1. The entire URL of the file you are using

https://github.com/tensorflow/models/tree/master/research/slim/BUILD

2. Describe the bug

The provided instruction to download the imagenet dataset with the provided scripts are broken. When attempting to build it with bazel, the following error rises:

(tf1-slim) D:\DL\datasets\ILSVRC2012\bazel_preprocess>bazel build :download_and_convert_imagenet

ERROR: Skipping ':download_and_convert_imagenet': error loading package '': Label '//devtools/python/blaze:pytype.bzl' is invalid because 'devtools/python/blaze' is not a package; perhaps you meant to put the colon here: '//:devtools/python/blaze/pytype.bzl'?

WARNING: Target pattern parsing failed.

ERROR: error loading package '': Label '//devtools/python/blaze:pytype.bzl' is invalid because 'devtools/python/blaze' is not a package; perhaps you meant to put the colon here: '//:devtools/python/blaze/pytype.bzl'?

INFO: Elapsed time: 0.155s

INFO: 0 processes.

FAILED: Build did NOT complete successfully (1 packages loaded)

3. Steps to reproduce

  1. Pull the repo
  2. bazel build :download_and_convert_imagenet

6. System information

  • Both Windows 10 and Fedora
  • TensorFlow installed from conda
  • TensorFlow version 1.14
  • Python version 3.6 and 3.7
  • Bazel version 3.1.0 (from conda)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.