The render_span_tree fixture signature changed from inner(event) (accepting a full transaction event dict) to inner(spans, root_span=None) (accepting a spans list). Existing callers in test_basic.py (lines 460, 599, 957, 1037, etc.) pass a full event dict like render_span_tree(transaction) which will now be incorrectly interpreted as a spans list, causing iteration over dict keys instead of spans and runtime errors.

A print(span) statement was added for debugging purposes but should be removed before merging. Debug print statements in test fixtures can clutter test output and indicate incomplete cleanup before PR submission.

In test_transactions, the span streaming branch (line 162) only asserts SPANDATA.SERVER_PORT not in span["attributes"], but the static branch (lines 203-204) also asserts SPANDATA.SERVER_ADDRESS not in span["data"]. This test coverage gap means the span streaming path doesn't verify that SERVER_ADDRESS is absent, potentially masking a behavioral difference between the two modes.

Also found at:

• tests/integrations/sqlalchemy/test_sqlalchemy.py:293

Inside the if span_streaming: block (line 901), the fake_record_sql_queries class contains an if span_streaming: check (lines 928-933). Since we're already inside the outer if span_streaming: block, span_streaming is always True, making lines 931-933 (else: self.span.start_timestamp = ...) dead code that will never execute.

Also found at:

• tests/integrations/sqlalchemy/test_sqlalchemy.py:989-991