Replies: 1 comment 5 replies
-
This combined with the high volume of LHRs you're uploading means sqlite just isn't a good fit for your needs anymore. sqlite locks the entire database for any writes which makes it a poor fit when your workload is lots of concurrent activity. LHCI already supports postgres and mysql (Heroku server example in the docs uses postgres), it's time to upgrade your installation beyond the sqlite default :) |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
The cron for deleting old builds ran at the same time lighthouse was running and probably caused the
SQLITE_BUSYerrorTo Reproduce
lhci uploadat the same timeExpected behavior
Delete cron works properly deleting several runs and lighthouse is able to save the run
Logs/Screenshots
Additional Context
Not sure if it's relevant but the branch/commit is unique and should be different from what the cron is deleting so I have no idea why it failed. For reference, here is the config we use for our server:
I have tested that the cron works on our lighthouse staging environment and it deleted the builds. We have thousands of branches on our lighthouse server prod so that could be a factor? i.e. takes longer time to delete everything and could conflict when running upload at the same time
Beta Was this translation helpful? Give feedback.
All reactions