Open alecandido opened 1 year ago
actually, should we transfer this to banana
? (which has even less traffic by the way, but this means it is working just fine, I'd say ...)
The issue at the moment is here, so I'd keep where it arose.
You can open a further issue in banana
, exporting the todo items from here.
Ok, blaming in Git it seems like that the problem described in https://github.com/NNPDF/yadism/pull/161#issuecomment-1335716316 it is my fault, but something I did one year ago.
This means that
yadism
is approximately unmaintained, and almost no development happened in the meanwhile...However, we need to drop asserts, since we never developed a suitable benchmark metric to automatically applied, see #83. For this, I propose:
banana
a no-assert mode, to be triggered by the workflowbanana
report extraction, such that we can upload them as artifacts in the CI.github/workflows/benchmark.yml
, deactivated with theon
value content in ef75c7a39546baa648fdadb503456f2ad8e3f29eEven though once you have the db and the extraction method this should be trivial (if well-documented), the workflow outcome should be intuitive to consume on its own. It is as much trivial to run the conversion in the CI and upload both.