FilOzone / FilOzone/foc-devnet
FOC Devnet scenarios run report (stability-frontier-curio)
- Dominant language
- Rust
- Stars
- 4
- Forks
- 5
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 15
Description
The **stability-frontier-curio** scenarios run **failed ❌**.
See [the workflow run](https://github.com/FilOzone/foc-devnet/actions/runs/33849043391) for details.
# Scenarios Tests
| Description | Data |
|-------------| ------------------------------------------------------------------- |
| Type | **stability-frontier-curio** |
| Date | 04-September-2026 09:51:48 GMT +0 |
| Status | PASS ✅:**5**, FAIL 🟥:**1**, Total:6 |
| CI run | [https://github.com/FilOzone/foc-devnet/actions/runs/33849043391](https://github.com/FilOzone/foc-devnet/actions/runs/33849043391) |
## Versions info
```
foc-devnet 1.0.0-rc.1
Commit: 458b7fe2a2837fd02071fe1777d3452cae3f9c8a
Branch: main
Built (UTC): 2026-09-04 09:10:54 UTC (40 minutes ago)
Built (Local): 2026-09-04 09:10:54 +00:00
default:code:lotus: https://github.com/filecoin-project/lotus.git, tag v1.36.2
default:code:curio: https://github.com/filecoin-project/curio.git, tag v1.28.6
default:code:filecoin-services: https://github.com/FilOzone/filecoin-services.git, tag v1.3.1
default:code:multicall3: https://github.com/mds1/multicall3.git, tag v3.1.0
```
## Resolved dependencies
| Dependency | Source | Version/ref | Commit | Overrides |
|---|---|---|---|---|
| curio | git | `main` | `0b18cf4ae4c041642a4450e7f10841c708b5f280` | - |
| filecoin-pin | npm | `2.0.0` | `-` | - |
| filecoin-services | git | `v1.4.0` | `4cbbea4a4f7da51ad674a1d9d122c6e677acfbec` | - |
| lotus | git | `v1.36.2` | `c6f4d02400dba55ebc5ab3677ef2ae5a5f4d1aef` | - |
| pdp | git_submodule | `fd76d609242a7065b44c0da21e9bb364c8c46691` | `fd76d609242a7065b44c0da21e9bb364c8c46691` | - |
| synapse-sdk | npm | `2.0.0` | `-` | - |
## Tests summary
✅ test_containers - PASS (0s)
```
[ OK ] container foc-20260904T0920_ZoomyLolo-lotus is running
[ OK ] container foc-20260904T0920_ZoomyLolo-lotus-miner is running
[ OK ] container foc-20260904T0920_ZoomyLolo-curio-1 is running
[ OK ] container foc-20260904T0920_ZoomyLolo-curio-2 is running
```
✅ test_basic_balances - PASS (0s)
```
[ OK ] cast is installed
[ OK ] at least one user exists
[ OK ] USER_1 FIL balance > 0
[ OK ] USER_1 USDFC balance > 0
[ OK ] USER_2 FIL balance > 0
[ OK ] USER_2 USDFC balance > 0
[ OK ] USER_3 FIL balance > 0
[ OK ] USER_3 USDFC balance > 0
```
✅ test_create_dataset_smoke - PASS (352s)
```
[ OK ] node is installed
[ OK ] install Synapse consumer runtime
[INFO] Synapse runtime: npm:@filoz/synapse-sdk@2.0.0
[INFO] Running createDataSet smoke script against devnet
[INFO] === Synapse data set creation probe ===
Provider: 1 (http://host.docker.internal:5711)
Plain ERC20 preparation: ready=false deposit=620000000070339200 approval=true
USDFC approval submitted: 0xfeb22dc6fbf10eaa6c20923347d843a1672abd23c7e216736a8651ac1378d08c
FilecoinPay deposit submitted: 0x034061d7daef77b3b87ccb7c0bab26f37d465181f14dfdcb107d54dff706c3f7
FWSS approval submitted: 0x76392c7ecdf5a90634266032aa46544c1cd47f3607f970a24b956290cb469ee1
Data set creation submitted: 0x0e07d429daad2630ef934f24f869cdbbee7e1500bf232ee39493f9c779ff6dd3
Data set created and verified: 1
[ OK ] createDataSet smoke test
```
✅ test_synapse_e2e - PASS (146s)
```
[ OK ] node is installed
[ OK ] install Synapse consumer runtime
[INFO] Synapse runtime: npm:@filoz/synapse-sdk@2.0.0
[INFO] Creating random file (20971520 bytes)
[ OK ] random_file created with exact size 20971520 bytes
[INFO] Running the Synapse-driven system E2E against devnet
[INFO] === Synapse system E2E ===
Network: devnet run=20260904T0920_ZoomyLolo
Fresh metadata: {"scenario":"system-e2e","run":"mtmrox5q-1rka"}
Phase 1: initialize account
Wallet: 0x47CC9101fD026fC112D7FADf6B3c9DF5bE7D4A8c
Phase 2: prepare payment account
Account preparation: ready=true deposit=0 approval=false
Prepared payment state: funds=10000000000000000000 available=10000000000000000000 lockup=0
Phase 3: upload and replicate
Uploading /tmp/synapse-e2e-5p3f8y9x/random_file (20971520 bytes) with 2 copy target
Provider selected: 1 (0x446339aE7245e3cd1FeD701b685C196C69af695e)
Provider selected: 2 (0xC60bc6fb60901c2d28ba6e4F8AD4915Bd2106497)
Upload progress: 10485760/20971520
Upload progress: 20971520/20971520
Primary stored: provider=1 piece=bafkzcibfqcapabiuuwbw4j3fajxirwml7a4bkrhop6gipo3u47drjeusofmnyitg3yaq
Replication: provider=2 piece=bafkzcibfqcapabiuuwbw4j3fajxirwml7a4bkrhop6gipo3u47drjeusofmnyitg3yaq status=pending
Replication: provider=2 piece=bafkzcibfqcapabiuuwbw4j3fajxirwml7a4bkrhop6gipo3u47drjeusofmnyitg3yaq status=complete
Replication complete: provider=2 piece=bafkzcibfqcapabiuuwbw4j3fajxirwml7a4bkrhop6gipo3u47drjeusofmnyitg3yaq
Commit submitted: provider=1 tx=0xedf22386be3c223fd1ec934b4c2a4bf7bc2fe2d2044a0cf41cb8e2c1371bfa94
Commit submitted: provider=2 tx=0x3321f02669e4acbd5a37c6d2b1f9bdb133c1c9850abf6e3f6d7084c4f9863904
Commit confirmed: provider=1 dataSet=3
Commit confirmed: provider=2 dataSet=2
Replication complete: piece=bafkzcibfqcapabiuuwbw4j3fajxirwml7a4bkrhop6gipo3u47drjeusofmnyitg3yaq
Phase 4: verify provider-agnostic retrieval
Provider-agnostic retrieval verified
Phase 5: verify every provider directly
Direct retrieval verified: provider=1 (20971520 bytes)
Direct retrieval verified: provider=2 (20971520 bytes)
Phase 6: verify observable on-chain state
Payment state: funds=9928000000000000000 available=8759899074709995604 lockup=1168095367526867200 rate=2778881568598
On-chain data set verified: id=3 provider=1 piece=0 rail=3
On-chain data set verified: id=2 provider=2 piece=0 rail=2
=== SUCCESS: complete two-provider Synapse journey verified ===
[ OK ] Synapse system E2E
```
✅ test_multi_copy_upload - PASS (217s)
```
[ OK ] node is installed
[ OK ] npm is installed
[ OK ] npm init
[ OK ] pin filecoin-pin 2.0.0
[ OK ] npm install
[INFO] Creating random file (20971520 bytes)
[ OK ] random_file created with exact size 20971520 bytes
[INFO] Running filecoin-pin multi-copy upload script against devnet
[INFO] filecoin-pin add attempt 1 (default multi-copy)
[INFO] Verified retrieval URL 1: http://host.docker.internal:5711/ipfs/bafybeicscvnp3dhanfl3yrgdavs35em6i4ycrkon5gvoggfnn6gfqdfj4q
[INFO] Verified retrieval URL 2: http://host.docker.internal:5715/ipfs/bafybeicscvnp3dhanfl3yrgdavs35em6i4ycrkon5gvoggfnn6gfqdfj4q
```
❌ test_caching_subsystem - TIMEOUT (200s)
```
[TIMEOUT] Test 'test_caching_subsystem' exceeded 200s limit
```
[Action Run link](https://github.com/FilOzone/foc-devnet/actions/runs/33849043391)
Contributor guide
No contributing guide indexed for this repository
Research direction
Open the linked GitHub Actions run and inspect the logs for test_caching_subsystem, which timed out after the 200-second limit. Compare it with the five passing scenario tests; done means the caching subsystem scenario completes within the limit and the full stability-frontier-curio run passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, node.js, rust
- Domain
- ci-cd, devops, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100