-
Notifications
You must be signed in to change notification settings - Fork 479
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
Kwxm/bench compare markdown #3471
Conversation
/benchmark |
/benchmark |
There seems to be something strange going on here. I modified
and then later
(the
Now f37f9cc is this commit by Amyas from the 21st of June. I have no idea what that's doing there! I'm also not sure if that's the commit that's actually checked when it's running the tests. |
It seems to be doing the same thing with Michael's PR #3340 (see the log at https://buildkite.com/input-output-hk/plutus-benchmark/builds/32#5b90cecf-0926-412d-a7bf-6e672ff991d5).
If it really is running the benchmarks in f37f9cc then that contains the old versions of the validation scripts (before @bezirg changed the flat encoding) which could have some bearing on the weird regression that I couldn't reproduce manually. |
Ah, I know what's up! Is anything updating the checkout? If it has a very old version of |
I don't know how that checkout is even created, though. |
Me neither. I have enough trouble with git on my own machine, so when it's being automatically run on a remote machine by a system I don't understand I'm lost. Can we just get it to update master before it does anything else? |
Experimenting a bit with the comparison automation script. /bench |
Also note there are conflicts with master now. |
/benchmark |
The last lot failed because of a problem with builtins in the flat format. Let's try again. /benchmark |
Hmmm. Getting lots of this in the output
Then lots of this:
Looks like it's replaying lots of changes when it does
I have no idea if that's sensible or not. |
Got a variable name wrong the last time. /benchmark |
Comparing benchmark results of '38d9354bde98e27e9756471aae062e7a56ab857e' (base) and '6eb2f00f5532013c8be24a8118ae280c12acee24' (PR)
|
/benchmark |
Comparing benchmark results of '38d9354bde98e27e9756471aae062e7a56ab857e' (base) and '6eb2f00f5532013c8be24a8118ae280c12acee24' (PR)
|
/benchmark |
Comparing benchmark results of '38d9354bde98e27e9756471aae062e7a56ab857e' (base) and 'b8a4b0833c124b70a33d49cc0b3c100918d62d1f' (PR)
|
This looks like it maybe kind of works, but it seems to be doing an awful lot of git stuff and I'm not convinced that it's using the correct commit for the base. I'm sure that can be improved, but my ignorance of git is too profound for me to have any idea of what the right thing to do is. Also, it still keeps going back to Anyway, the comparison script is doing the right thing, which is what this PR was supposed to be about. I should probably extract that and make a new PR that doesn't touch any of the CI stuff (later: done in #3494). |
/benchmark |
Comparing benchmark results of '38d9354bde98e27e9756471aae062e7a56ab857e' (base) and '66124c163084095f1dd6bd5720788cd055831946' (PR)
|
Do we still need this? |
I think the underlying issue hasn't been resolved yet, so let's keep it for the time being. |
Just testing.
Pre-submit checklist:
Pre-merge checklist: