Skip to content

libriarian: new library generation complains about non-empty sub-directories of the new library #2687

@vchudnov-g

Description

@vchudnov-g

I get an unexpected warning that does not halt execution, but it's surprising given that this happens during new library generation:

level=WARN msg="failed to remove directory, it may not be empty" dir=/usr/local/[REDACTED]/google-cloud-python/packages/google-cloud-hypercomputecluster/docs err="remove /usr/local/[REDACTED]/google-cloud-python/packages/google-cloud-hypercomputecluster/docs: directory not empty"

level=WARN msg="failed to remove directory, it may not be empty" dir=/usr/local/[REDACTED]/google-cloud-python/packages/google-cloud-hypercomputecluster err="remove /usr/local/google/[REDACTED]/google-cloud-python/packages/google-cloud-hypercomputecluster: directory not empty"

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions