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

cmd/devp2p/internal/ethtest: skip large tx test on github build #28794

Merged
merged 6 commits into from
Jan 12, 2024

Conversation

s1na
Copy link
Contributor

@s1na s1na commented Jan 11, 2024

This test was failling consistently on the github 32-bit build probably due to slow IO. Skipping it for that green check.

@fjl fjl changed the title devp2p/internal: skip large tx test on 32-bit builds cmd/devp2p/internal/ethtest: skip large tx test on 32-bit builds Jan 11, 2024
if bits.UintSize > 32 {
tests = append(tests, utesting.Test{Name: "TestLargeTxRequest", Fn: s.TestLargeTxRequest})
}
return tests
Copy link
Contributor

@fjl fjl Jan 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer if we skip the test in the actual Go unit test that runs this instead of excluding it from the list here. The tests are executed here:

result := utesting.RunTests([]utesting.Test{{Name: test.Name, Fn: test.Fn}}, os.Stdout)

So please add a condition there, like

if bits.UintSize == 32 && test.Name == "TestLargeTxRequest" {
    t.Skip()
}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to use different semantics. Instead of
"Are we running on 32-bit? If so, skip", the logic should be
"Are we running with the tag short? If so, skip".

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I.e

	if testing.Short() && test.Name == "TestLargeTxRequest"{
		t.Skip("skipped in short-mode")
	}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please take another look. I refactored so skipping is based both on short tag or 386 arch. This is similar to how we decide on skipping the state tests:

if testing.Short() {
return "skipped in -short mode", false
}
if isWin32 {
return "skipped on 32bit windows", false
}

@holiman
Copy link
Contributor

holiman commented Jan 12, 2024 via email

@s1na
Copy link
Contributor Author

s1na commented Jan 12, 2024

Imo use only short. Everything else is wrong :)

Done

@fjl
Copy link
Contributor

fjl commented Jan 12, 2024

Waiting for builds

@s1na s1na changed the title cmd/devp2p/internal/ethtest: skip large tx test on 32-bit builds cmd/devp2p/internal/ethtest: skip large tx test on github build Jan 12, 2024
Copy link
Contributor

@holiman holiman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@holiman holiman merged commit a608c0a into ethereum:master Jan 12, 2024
2 of 3 checks passed
@holiman holiman added this to the 1.13.11 milestone Jan 12, 2024
Dergarcon pushed a commit to specialmechanisms/mev-geth-0x2mev that referenced this pull request Jan 31, 2024
…reum#28794)

This test was failling consistently on the github 32-bit build probably due to slow IO. Skipping it for that green check.
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.

3 participants