We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
DESCRIPTION
cosbench-openio build fails saying directory 'test' not found.
REPRODUCE PROCEDURE
Just try to build following BUILD.md, and you would see an error for cosbench-openio.
ANALYSYS and SUGGESTED RESOLUTION
Obviously, this is because dev/cosbench-openio/.classpath contains a classpath element'test' but 'test' directory does not exist.
dev/cosbench-openio/.classpath
So, there are 2 resolutions:
.classpath
IMHO, 2. is better because there is no test code, and like the case of #413, a chunk of PR from @Nathaniel7687 resolves this issue.
https://github.com/intel-cloud/cosbench/pull/373/files?file-filters%5B%5D=dotfile&hide-deleted-files=true#diff-79b4a0076c9d63216bc4a7701d85aed387ea2481f854871c83ccabc1d69cf480
The text was updated successfully, but these errors were encountered:
No branches or pull requests
DESCRIPTION
cosbench-openio build fails saying directory 'test' not found.
REPRODUCE PROCEDURE
Just try to build following BUILD.md, and you would see an error for cosbench-openio.
ANALYSYS and SUGGESTED RESOLUTION
Obviously, this is because
dev/cosbench-openio/.classpath
contains a classpath element'test' but 'test' directory does not exist.So, there are 2 resolutions:
.classpath
IMHO, 2. is better because there is no test code, and like the case of #413,
a chunk of PR from @Nathaniel7687 resolves this issue.
https://github.com/intel-cloud/cosbench/pull/373/files?file-filters%5B%5D=dotfile&hide-deleted-files=true#diff-79b4a0076c9d63216bc4a7701d85aed387ea2481f854871c83ccabc1d69cf480
The text was updated successfully, but these errors were encountered: