R
RunPod2w ago
xixi

Serverless Endpoint using official github repo Stuck at "Waiting for building"

Hi, I'm deploying a serverless endpoint using the official github repo runpod-workers/worker-template. I just fork this repo and add one line in dockerfile "RUN pip install --upgrade pip && pip install uv" WITHOUT any other changes. Build completes successfully with no errors in the logs. However, during the testing phase, the status remains at "Waiting for building" indefinitely. No test logs are generated. After about an hour, the process cancels automatically. I've tried increasing the max workers to 2 and allowing multiple GPU types, but the issue persists. Could someone assist me in identifying what's causing the worker to hang during initialization?
No description
9 Replies
Dj
Dj2w ago
Are you still having this issue? Can you download that log and send it here?
curtis3204
curtis32042w ago
@Dj I also have that issue, but i wait for building sreverless for a long time , and it still "pending", "waiting for build"
curtis3204
curtis32042w ago
No description
xixi
xixiOP2w ago
i fork worker-basic instead and deploy again, it works. i will modify based on the worker-basic repo instead. thanks.
xixi
xixiOP2w ago
https://github.com/runpod-workers/worker-basic this repo works https://github.com/runpod-workers/worker-template this repo will stuck in waiting for building (testing process with no test logs)
GitHub
GitHub - runpod-workers/worker-basic
Contribute to runpod-workers/worker-basic development by creating an account on GitHub.
GitHub
GitHub - runpod-workers/worker-template: Starting point to build yo...
Starting point to build your own custom serverless endpoint - runpod-workers/worker-template
yhlong00000
yhlong000002w ago
Just want a quick feedback, worker basic vs worker template, which one you feel is easier to start?
xixi
xixiOP2w ago
actually, they are all easy to start, however, i don't know why worker template doesn't work (directly fork and deploy, stuck in waiting for build' testing process)
Dj
Dj2w ago
I think we know why this bug happens, I'll get it fixed in the morning.
Jason
Jason2w ago
delete the /.runpod/tests.json file

Did you find this page helpful?