Skip to content

ZK Prove Any: tracking PR#4361

Draft
pmikolajczyk41 wants to merge 275 commits intomasterfrom
zk-prove-any/sp1-runner
Draft

ZK Prove Any: tracking PR#4361
pmikolajczyk41 wants to merge 275 commits intomasterfrom
zk-prove-any/sp1-runner

Conversation

@pmikolajczyk41
Copy link
Copy Markdown
Member

@pmikolajczyk41 pmikolajczyk41 commented Feb 11, 2026

NOT INTENDED FOR MERGING (YET)

pulls in OffchainLabs/wasmer#34

@pmikolajczyk41 pmikolajczyk41 self-assigned this Feb 11, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented Feb 11, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 33.15%. Comparing base (6dce8d1) to head (e43919f).

❗ There is a different number of reports uploaded between BASE (6dce8d1) and HEAD (e43919f). Click for more details.

HEAD has 8 uploads less than BASE
Flag BASE (6dce8d1) HEAD (e43919f)
15 7
Additional details and impacted files
@@             Coverage Diff             @@
##           master    #4361       +/-   ##
===========================================
- Coverage   52.15%   33.15%   -19.00%     
===========================================
  Files         506      506               
  Lines       73739    60415    -13324     
===========================================
- Hits        38458    20033    -18425     
- Misses      30083    36846     +6763     
+ Partials     5198     3536     -1662     

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 11, 2026

❌ 8 Tests Failed:

Tests completed Failed Passed Skipped
5034 8 5026 0
View the top 3 failed tests by shortest run time
TestChallengeToFailedTooFar
Stack Traces | 0.080s run time
... [CONTENT TRUNCATED: Keeping last 20 lines]
    challenge_test.go:41: goroutine 3174 [running]:
        runtime/debug.Stack()
        	/opt/hostedtoolcache/go/1.25.9/x64/src/runtime/debug/stack.go:26 +0x5e
        github.com/offchainlabs/nitro/util/testhelpers.RequireImpl({0x2dec870, 0xc001206fc0}, {0x2dc8ac0, 0xc00124d650}, {0x0, 0x0, 0x0})
        	/home/runner/work/nitro/nitro/util/testhelpers/testhelpers.go:29 +0x9f
        github.com/offchainlabs/nitro/staker/legacy.Require(0xc001206fc0, {0x2dc8ac0, 0xc00124d650}, {0x0, 0x0, 0x0})
        	/home/runner/work/nitro/nitro/staker/legacy/common_test.go:14 +0x5d
        github.com/offchainlabs/nitro/staker/legacy.DeployOneStepProofEntry(0xc001206fc0, 0xc003b9c7e0, {0x2de0490, 0xc003771c08})
        	/home/runner/work/nitro/nitro/staker/legacy/challenge_test.go:41 +0x1fd
        github.com/offchainlabs/nitro/staker/legacy.runChallengeTest(0xc001206fc0, 0xc005df1580, {0x2de3118, 0xc005df15a0}, 0x1, 0x0, 0xb)
        	/home/runner/work/nitro/nitro/staker/legacy/challenge_test.go:135 +0x425
        github.com/offchainlabs/nitro/staker/legacy.TestChallengeToFailedTooFar(0xc001206fc0)
        	/home/runner/work/nitro/nitro/staker/legacy/challenge_test.go:303 +0x118
        testing.tRunner(0xc001206fc0, 0x2be5060)
        	/opt/hostedtoolcache/go/1.25.9/x64/src/testing/testing.go:1934 +0xea
        created by testing.(*T).Run in goroutine 1
        	/opt/hostedtoolcache/go/1.25.9/x64/src/testing/testing.go:1997 +0x465
        
    challenge_test.go:41: �[31;1m [] replacement transaction underpriced �[0;0m
--- FAIL: TestChallengeToFailedTooFar (0.08s)
TestRedisProduceComplex/one_producer,_some_consumers_killed,_one_retrying_consumer_should_take_over_their_work
Stack Traces | 2.009s run time
... [CONTENT TRUNCATED: Keeping last 20 lines]
�[36mDEBUG�[0m[04-27|15:49:04.471] checkResponses                           �[36mresponded�[0m=0  �[36merrored�[0m=0 �[36mchecked�[0m=5
�[36mDEBUG�[0m[04-27|15:49:04.477] redis producer: check responses starting
�[36mDEBUG�[0m[04-27|15:49:04.478] checkResponses                           �[36mresponded�[0m=0  �[36merrored�[0m=0 �[36mchecked�[0m=5
�[36mDEBUG�[0m[04-27|15:49:04.484] redis producer: check responses starting
�[36mDEBUG�[0m[04-27|15:49:04.484] checkResponses                           �[36mresponded�[0m=0  �[36merrored�[0m=0 �[36mchecked�[0m=5
�[36mDEBUG�[0m[04-27|15:49:04.489] redis producer: check responses starting
�[36mDEBUG�[0m[04-27|15:49:04.490] checkResponses                           �[36mresponded�[0m=0  �[36merrored�[0m=0 �[36mchecked�[0m=5
�[36mDEBUG�[0m[04-27|15:49:04.496] redis producer: check responses starting
�[36mDEBUG�[0m[04-27|15:49:04.496] request timed out waiting for response   �[36mmsgId�[0m=1777304942492-19 �[36mallowedOldestId�[0m=1777304942496-0
�[36mDEBUG�[0m[04-27|15:49:04.496] request timed out waiting for response   �[36mmsgId�[0m=1777304942492-18 �[36mallowedOldestId�[0m=1777304942496-0
�[36mDEBUG�[0m[04-27|15:49:04.496] request timed out waiting for response   �[36mmsgId�[0m=1777304942492-20 �[36mallowedOldestId�[0m=1777304942496-0
�[36mDEBUG�[0m[04-27|15:49:04.496] request timed out waiting for response   �[36mmsgId�[0m=1777304942492-17 �[36mallowedOldestId�[0m=1777304942496-0
�[36mDEBUG�[0m[04-27|15:49:04.496] request timed out waiting for response   �[36mmsgId�[0m=1777304942492-21 �[36mallowedOldestId�[0m=1777304942496-0
�[36mDEBUG�[0m[04-27|15:49:04.496] checkResponses                           �[36mresponded�[0m=0  �[36merrored�[0m=5 �[36mchecked�[0m=5
    pubsub_test.go:385: Unexpected error while awaiting responses, producer: 0, response: 71, err: error getting response, request has been waiting for too long
    pubsub_test.go:385: Unexpected error while awaiting responses, producer: 0, response: 72, err: error getting response, request has been waiting for too long
    pubsub_test.go:385: Unexpected error while awaiting responses, producer: 0, response: 73, err: error getting response, request has been waiting for too long
    pubsub_test.go:385: Unexpected error while awaiting responses, producer: 0, response: 74, err: error getting response, request has been waiting for too long
    pubsub_test.go:385: Unexpected error while awaiting responses, producer: 0, response: 75, err: error getting response, request has been waiting for too long
--- FAIL: TestRedisProduceComplex/one_producer,_some_consumers_killed,_one_retrying_consumer_should_take_over_their_work (2.01s)
TestRedisProduceComplex/one_producer,_some_consumers_killed,_one_retrying_consumer_should_take_over_their_work
Stack Traces | 2.080s run time
... [CONTENT TRUNCATED: Keeping last 20 lines]
�[36mDEBUG�[0m[04-27|15:43:56.304] redis producer: check responses starting
�[36mDEBUG�[0m[04-27|15:43:56.305] checkResponses                           �[36mresponded�[0m=0  �[36merrored�[0m=0 �[36mchecked�[0m=7
�[36mDEBUG�[0m[04-27|15:43:56.310] redis producer: check responses starting
�[36mDEBUG�[0m[04-27|15:43:56.310] request timed out waiting for response   �[36mmsgId�[0m=1777304634308-22 �[36mallowedOldestId�[0m=1777304634310-0
�[36mDEBUG�[0m[04-27|15:43:56.310] request timed out waiting for response   �[36mmsgId�[0m=1777304634308-20 �[36mallowedOldestId�[0m=1777304634310-0
�[36mDEBUG�[0m[04-27|15:43:56.311] request timed out waiting for response   �[36mmsgId�[0m=1777304634308-26 �[36mallowedOldestId�[0m=1777304634310-0
�[36mDEBUG�[0m[04-27|15:43:56.311] request timed out waiting for response   �[36mmsgId�[0m=1777304634308-23 �[36mallowedOldestId�[0m=1777304634310-0
�[36mDEBUG�[0m[04-27|15:43:56.311] request timed out waiting for response   �[36mmsgId�[0m=1777304634308-21 �[36mallowedOldestId�[0m=1777304634310-0
�[36mDEBUG�[0m[04-27|15:43:56.311] request timed out waiting for response   �[36mmsgId�[0m=1777304634308-25 �[36mallowedOldestId�[0m=1777304634310-0
�[36mDEBUG�[0m[04-27|15:43:56.311] request timed out waiting for response   �[36mmsgId�[0m=1777304634308-24 �[36mallowedOldestId�[0m=1777304634310-0
�[36mDEBUG�[0m[04-27|15:43:56.311] checkResponses                           �[36mresponded�[0m=0  �[36merrored�[0m=7 �[36mchecked�[0m=7
    pubsub_test.go:385: Unexpected error while awaiting responses, producer: 0, response: 76, err: error getting response, request has been waiting for too long
    pubsub_test.go:385: Unexpected error while awaiting responses, producer: 0, response: 77, err: error getting response, request has been waiting for too long
    pubsub_test.go:385: Unexpected error while awaiting responses, producer: 0, response: 78, err: error getting response, request has been waiting for too long
    pubsub_test.go:385: Unexpected error while awaiting responses, producer: 0, response: 79, err: error getting response, request has been waiting for too long
    pubsub_test.go:385: Unexpected error while awaiting responses, producer: 0, response: 80, err: error getting response, request has been waiting for too long
    pubsub_test.go:385: Unexpected error while awaiting responses, producer: 0, response: 81, err: error getting response, request has been waiting for too long
    pubsub_test.go:385: Unexpected error while awaiting responses, producer: 0, response: 82, err: error getting response, request has been waiting for too long
�[36mDEBUG�[0m[04-27|15:43:56.384] Error destroying a stream group          �[36merror�[0m="dial tcp 127.0.0.1:36169: connect: connection refused"
--- FAIL: TestRedisProduceComplex/one_producer,_some_consumers_killed,_one_retrying_consumer_should_take_over_their_work (2.08s)

📣 Thoughts on this report? Let Codecov know! | Powered by Codecov

@pmikolajczyk41 pmikolajczyk41 marked this pull request as draft February 12, 2026 12:56
@pmikolajczyk41
Copy link
Copy Markdown
Member Author

state for 17 II 2026:

  • 51 files changed
  • +16'809, -8 lines

@pmikolajczyk41
Copy link
Copy Markdown
Member Author

state for 21 IV 2026:

56 files changed
+8'968, -1'031 lines

pmikolajczyk41 and others added 24 commits April 23, 2026 12:26
…iling

Makify SP1. Record a few types of blocks.
Signed-off-by: Igor Braga <5835477+bragaigor@users.noreply.github.com>
When you invoke $(MAKE) in a recipe, make automatically:
1. Sets MAKEFLAGS (the make variable).
2. Exports MAKEFLAGS as an environment variable.
3. The sub-make reads MAKEFLAGS from the environment at startup and applies
those flags.

Passing $(MAKEFLAGS) as positional arguments (make $(MAKEFLAGS)) is redundant,
 not additive — it's the same info via a second channel. And it's actively
harmful because of the argv quoting rules: MAKEFLAGS stores short flags
concatenated without a leading dash (e.g. w, sw, j4), so when interpolated
onto a command line, w becomes a target, sw becomes a target, etc. The
env-based path has no such ambiguity because make parses it itself.

Signed-off-by: Igor Braga <5835477+bragaigor@users.noreply.github.com>
Sync SP1 README with new Makefile workflow; add run target
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants