Temporarily disable ffead

[michaelhixson]

The last two runs in the Citrine environment failed because of problems induced by ffead. We don't know that ffead is doing anything wrong -- even if it is, the TFB toolset is to blame for letting that ruin the run -- but we would like to continue benchmarking other frameworks while we figure this out.

[NateBrady23]

@sumeetchhetri just an FYI on this

[sumeetchhetri]

@nbrady-techempower, I have been experimenting with a few custom allocators and upgrading a few libraries in the master branch, maybe that caused the issue, will create a new PR with the fixes and the passing verify steps to fix this, in the meanwhile, this should anyways be handled in the tfb toolset for sure to avoid possible future issues with test runs.

[NateBrady23]

@sumeetchhetri I must have missed this in the review, but your dependencies (including the framework itself) should be a specific commit or version such that breaking changes aren't introduced without going through a PR. Please make sure all your dependencies are locked down as best as possible and I'll review more closely next time.

this should anyways be handled in the tfb toolset for sure to avoid possible future issues with test runs

We understand this: "the TFB toolset is to blame for letting that ruin the run" We're looking into the issue.

[NateBrady23]

@sumeetchhetri Also, if you happen to know what the offending commit was that you think may have caused this, that would be helpful in tracking down the bug in the the toolset.