bug: lfs failure after clone

[bfield308]

Description

There is a bug with pulling the lfs after cloning the hdf-libs repo. Users receive the error in Actual Results. This has been attemped a couple of times on different days/times and with different devices in an attempt to rule out system issues and GitHub API / LFS capacity constraints.

Reproduce the error

• start in a fresh directory
• git clone https://github.com/mitre/hdf-libs.git && cd hdf-libs
• git lfs fetch --all && git lfs checkout

Expected results

User should retrieve all 34 lfs files associated with the repo

Actual Results

34 objects found, done.                                                                                                                                         
Fetching all references...
batch response: This repository exceeded its LFS budget. The account responsible for the budget should increase it to restore access.                           
error: failed to fetch some objects from 'https://github.com/mitre/hdf-libs.git/info/lfs'

User system information

N/A - this is a GitHub issue

[wdower]

We'd used LFS initially to track large test fixtures for use building out the initial converter set where we wanted rich and varied data to make sure we caught common edge cases. By the time we hit the LFS cap for the org, that work was complete. I moved the repo away from using LFS by release 3.0.1 (dca7094) and instead just used minimal fixtures for testing on the assumption that the wider userbase and dev base didn't need to cart around 100MB of fixtures for converters on every clone; they could just grab a decent fixture from open sources like I did if they needed to actually do work on a given converter.

I can reassemble the fixtures list and add it as a release package. That would let us avoid hammering the org LFS and let only those who need them download larger fixtures.