Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] Failing test on master, CI didn't catch it. #6726

Closed
gui1117 opened this issue Dec 2, 2024 · 2 comments
Closed

[CI] Failing test on master, CI didn't catch it. #6726

gui1117 opened this issue Dec 2, 2024 · 2 comments

Comments

@gui1117
Copy link
Contributor

gui1117 commented Dec 2, 2024

As reported by @clangenb https://github.com/paritytech/polkadot-sdk/pull/6294/files#r1822860138

A test on master is failing. The test is in a file conditioned by runtime-benchmarks, and is generated by construct_runtime:

frame_support::construct_runtime!(

From what I see in the merge queue, the job running the benchmarking test is: https://github.com/paritytech/polkadot-sdk/actions/runs/12106844624/job/33753083856

The command is: forklift cargo nextest run --workspace --features runtime-benchmarks benchmark --locked --cargo-profile testnet --cargo-quiet

but this run only the test that contains the word benchmark. The test name is mock::test_genesis_config_builds so it was skipped.

@bkchr
Copy link
Member

bkchr commented Dec 2, 2024

Yeah the benchmark is filtering out only the tests which are generated by the benchmarking macros. IMO the best would be to extend the call with the crates that contain benchmark. Still not the best and some tests could get skipped, but generally tests should not be hidden behind the runtime-benchmarks feature any way.

@gui1117
Copy link
Contributor Author

gui1117 commented Dec 3, 2024

I agree, it is good convention that test should not be hidden by runtime-benchmarks features. Even for pallet session benchmarking, the mock doesn't need to be hidden by runtime-benchmarks feature.

@gui1117 gui1117 closed this as completed Dec 3, 2024
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

No branches or pull requests

2 participants