Skip to content

Move VOL tools testing to the library #5117

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

Open
derobins opened this issue Nov 14, 2024 · 0 comments · May be fixed by #5515
Open

Move VOL tools testing to the library #5117

derobins opened this issue Nov 14, 2024 · 0 comments · May be fixed by #5515
Assignees
Labels
Component - Testing Code in test or testpar directories, GitHub workflows Component - Tools Command-line tools like h5dump, includes high-level tools HDFG-internal Internally coded for use by the HDF Group Priority - 1. High These are important issues that should be resolved in the next release
Milestone

Comments

@derobins
Copy link
Member

We improved the tools testing to allow VOL connectors to be used. This needs to be moved to the main library from the VOL testing repo.

@derobins derobins added Component - Testing Code in test or testpar directories, GitHub workflows Component - Tools Command-line tools like h5dump, includes high-level tools Priority - 1. High These are important issues that should be resolved in the next release Type - New Feature labels Nov 14, 2024
@derobins derobins added this to the 2.0.0 milestone Nov 14, 2024
@nbagha1 nbagha1 added the HDFG-internal Internally coded for use by the HDF Group label Mar 14, 2025
@nbagha1 nbagha1 assigned mattjala and unassigned glennsong09 Mar 14, 2025
@jhendersonHDF jhendersonHDF linked a pull request May 16, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component - Testing Code in test or testpar directories, GitHub workflows Component - Tools Command-line tools like h5dump, includes high-level tools HDFG-internal Internally coded for use by the HDF Group Priority - 1. High These are important issues that should be resolved in the next release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants