You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even 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.
The text was updated successfully, but these errors were encountered:
Ok, blaming in Git it seems like that the problem described in #161 (comment) 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 ef75c7aEven 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.
The text was updated successfully, but these errors were encountered: