Skip to content
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

artifact_extractor does not accept absolute path #343

Open
lolski opened this issue May 4, 2022 · 0 comments
Open

artifact_extractor does not accept absolute path #343

lolski opened this issue May 4, 2022 · 0 comments

Comments

@lolski
Copy link
Member

lolski commented May 4, 2022

The artifact_extractor will fail to extract artifacts when the output path is specified as absolute path like below. Moreover, the failure is silent (ie., without throwing any error):

bazel run //test:typedb-extractor-linux /home/grabl/$GRABL_REPO/dist/typedb-all-linux/

If a relative path is supplied instead, the rule will work successfully:

bazel run //test:typedb-extractor-linux dist/typedb-all-linux/

This isn't ideal and the rule should be made to work for any valid file paths, both absolute and relative.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant