-
Notifications
You must be signed in to change notification settings - Fork 109
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
Put out benchmark fires #404
Conversation
db119df
to
a5b50f4
Compare
@Centril, fixed the issue you pointed out. @mamcx, I've tried to revert as little of your commit as possible -- only the stuff in the Waiting on https://github.com/clockworklabs/SpacetimeDB/actions/runs/6473567337/job/17576553107 ... #403 and #402 should be fixed, #401 I still have no idea about. |
Ok, now this is ready for merge. I still haven't fixed the recompilation issue (#401) but I'll leave that for another day. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to just go ahead and merge this as I want to unblock benchmarks on branches / PRs.
Looks like it didn't address #402: https://github.com/clockworklabs/SpacetimeDB/actions/runs/6496776998/job/17644465697 |
Ah probably because there's pre-existing cache without those newly declared files. Might be worth cleaning cache manually. |
Went through caches and deleted all those from master; let's see if that helps... |
Nope somehow still same error even when it clearly says "cache not found": https://github.com/clockworklabs/SpacetimeDB/actions/runs/6497076599/job/17645385541 |
Attempting to address #401 #402 #403