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

Enable Backfill in E2E #13524

Merged
merged 8 commits into from
Jan 26, 2024
Merged

Enable Backfill in E2E #13524

merged 8 commits into from
Jan 26, 2024

Conversation

nisdas
Copy link
Member

@nisdas nisdas commented Jan 25, 2024

What type of PR is this?

E2E Improvement

What does this PR do? Why is it needed?

This enables backfill for our E2E runs by adding it to our dev mode.

Which issues(s) does this PR fix?

N.A

Other notes for review

@nisdas nisdas added Ready For Review A pull request ready for code review E2E Tests End-To-End testing labels Jan 25, 2024
@nisdas nisdas requested a review from a team as a code owner January 25, 2024 04:19
@nisdas nisdas requested review from nalepae, potuz and rkapka January 25, 2024 04:19
beacon-chain/sync/backfill/status.go Show resolved Hide resolved
@@ -0,0 +1,38 @@
package flags
Copy link
Contributor

Choose a reason for hiding this comment

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

What is the reason to break flags out into a separate package?

Copy link
Member Author

Choose a reason for hiding this comment

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

We need to import the backfill flag to our feature package, since we want it as part of --dev. If you dont have a separate package, build fails due to dependency cycles

@nisdas nisdas added this pull request to the merge queue Jan 26, 2024
Merged via the queue into develop with commit 22b6d17 Jan 26, 2024
17 checks passed
@nisdas nisdas deleted the enableBackfillE2E branch January 26, 2024 05:01
@@ -283,7 +283,7 @@ func (node *BeaconNode) Start(ctx context.Context) error {
// on our features or the beacon index is a multiplier of 2 (idea is to split nodes
// equally down the line with one group having feature flags and the other without
// feature flags; this is to allow A-B testing on new features)
if !config.TestFeature || index%2 == 0 {
if !config.TestFeature || index != 1 {

Choose a reason for hiding this comment

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

The comment above indicates this was supposed to be only for multiples of 2 - which one is intended?

Copy link
Member Author

Choose a reason for hiding this comment

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

Will fix the comment, but the current intent is to only have 1 node running as a control rather than splitting it down the line

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E2E Tests End-To-End testing Ready For Review A pull request ready for code review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants