chore(execute): fix execute hive mode

[spencer-tb]

🗒️ Description

Fixes execute hive mode, specifically for adding the execute-blobs simulator to the hive CI.

🔗 Related Issues or PRs

Blocker for: ethpandaops/fusaka-devnets#115
Requires: ethereum/hive#1365

✅ Checklist

• All: Ran fast tox checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:

  uvx tox -e static

• All: PR title adheres to the repo standard - it will be used as the squash commit message and should start type(scope):.
• All: Considered adding an entry to CHANGELOG.md.
• All: Considered updating the online docs in the ./docs/ directory.
• All: Set appropriate labels for the changes (only maintainers can apply labels).

Cute Animal Picture

[marioevz]

This doesn't look right, if the cwd is ./execution-specs/ I think it should not do relative paths.

What's the error you are seeing that you are trying to fix with this?

[spencer-tb]

Fixed thanks!

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.07%. Comparing base (c3e5260) to head (ddbef39).
⚠️ Report is 2 commits behind head on forks/osaka.
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@             Coverage Diff              @@
##           forks/osaka    #1698   +/-   ##
============================================
  Coverage        86.07%   86.07%           
============================================
  Files              743      743           
  Lines            44078    44078           
  Branches          3894     3894           
============================================
  Hits             37938    37938           
  Misses            5659     5659           
  Partials           481      481           

Flag	Coverage Δ
unittests	86.07% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[danceratopz]

Hey @spencer-tb! Can you check whether adding the test_case_description fixture is really necessary?

[danceratopz]

This will return the test ID, not the test case description as expected by Hive. Is this necessary? Perhaps you're intentionally overwriting this fixture?

execution-specs/packages/testing/src/execution_testing/cli/pytest_commands/plugins/shared/execute_fill.py

Lines 183 to 205 in 15b5cfd

	@pytest.fixture(scope="function")
	def test_case_description(request: pytest.FixtureRequest) -> str:
	"""
	Fixture to extract and combine docstrings from the test class and the test
	function.
	"""
	description_unavailable = "No description available - add a docstring to the python test class or function."
	test_class_doc = ""
	test_function_doc = ""
	if hasattr(request.node, "cls"):
	test_class_doc = (
	f"Test class documentation:\n{request.cls.__doc__}"
	if request.cls
	else ""
	)
	if hasattr(request.node, "function"):
	test_function_doc = (
	f"{request.function.__doc__}" if request.function.__doc__ else ""
	)
	if not test_class_doc and not test_function_doc:
	return description_unavailable
	combined_docstring = f"{test_class_doc}\n\n{test_function_doc}".strip()
	return combined_docstring