hashgraph / hashgraph/solo-weaver
E2E: sequence ordering — 3 jobs at same phase run in ascending order
- Dominant language
- Go
- Stars
- 3
- Forks
- 0
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 47
Description
**Epic:** #1082
Package 3 job descriptors at the same phase with `sequence: 30, 10, 20`. Each job writes its sequence number and timestamp to a shared volume or log. Assert execution order is 10 → 20 → 30.
## Acceptance Criteria
- [ ] Jobs run in ascending sequence order (10 → 20 → 30)
- [ ] Test covers both upgrade (frozen) and install (pre-install) contexts
- [ ] Deterministic on 5 consecutive runs
Contributor guide
Research direction
Start by reviewing epic #1082 and locating the repository's E2E harness for job descriptors. Add coverage for three same-phase jobs in upgrade and install contexts, then run the test five consecutive times to confirm deterministic 10 → 20 → 30 ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100