Skip to content

Worker state persistence problem #64

@Rutik7066

Description

@Rutik7066

When run tests in sequence for bedrock, workers fails to resume.

Image

golem server logs.txt

Steps to reproduce

1. git clone https://github.com/Rutik7066/golem-llm-2.git  && git checkout bedrock 
2. cd golem-llm-2 &&  cargo make build && cargo make test-components 
3. golem server clean && golem server run
4. cd test 
5. golem app build -b bedrock-debug &&
golem app deploy -b bedrock-debug &&
golem worker new -e  GOLEM_LLM_LOG=trace -e AWS_ACCESS_KEY_ID=AWS_ACCESS_KEY_ID  -e AWS_SECRET_ACCESS_KEY=AWS_SECRET_ACCESS_KEY  -e AWS_REGION=ap-south-1  test:llm/twork
6.  golem worker invoke -s test:llm/twork test1 && sleep 3 &&
golem worker invoke -s test:llm/twork test2 && sleep 3 &&
golem worker invoke -s test:llm/twork test3 && sleep 3 &&
golem worker invoke -s test:llm/twork test4 && sleep 3 &&
golem worker invoke -s test:llm/twork test5 && sleep 3 &&
golem worker invoke -s test:llm/twork test6 && sleep 3 &&
golem worker invoke -s test:llm/twork test7

Golem server version 1.2.5

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions