Skip to content

[Merged by Bors] - Use latest tags for nethermind and geth in the execution engine integration test#3303

Closed
divagant-martian wants to merge 8 commits intosigp:unstablefrom
divagant-martian:test
Closed

[Merged by Bors] - Use latest tags for nethermind and geth in the execution engine integration test#3303
divagant-martian wants to merge 8 commits intosigp:unstablefrom
divagant-martian:test

Conversation

@divagant-martian
Copy link
Contributor

@divagant-martian divagant-martian commented Jul 1, 2022

Issue Addressed

Currently the execution-engine-integration test uses latest master for nethermind and geth, and right now the test fails using the latest unreleased commits.

Proposed Changes

Fix the nethermind and geth revisions the test uses to the latest tag in each repo. This way we are not continuously testing unreleased code, which might even get reverted, and reduce the failures only to releases in each one.
Also improve error handling of the commands used to manage the git repos.

Additional Info

na

@divagant-martian divagant-martian changed the title only exec integration test Use latest tags for nethermind and geth in the execution engine integration test Jul 2, 2022
@divagant-martian divagant-martian marked this pull request as ready for review July 2, 2022 11:57
Copy link
Member

@michaelsproul michaelsproul left a comment

Choose a reason for hiding this comment

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

Approving and merging to unblock CI, thanks Diva!

// Update the branch
assert!(build_utils::update_branch(&repo_dir, GETH_BRANCH));
// Get the latest tag on the branch
let last_release = build_utils::get_latest_release(&repo_dir).unwrap();
Copy link
Member

Choose a reason for hiding this comment

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

I think this is slightly awkward in the case where repo_dir already existed and was checked out to a prior release. The git describe will describe the HEAD so it will just return the same tag back, and the repo will be stuck until the user manually intervenes. I don't think this is a problem for CI, however.

I guess the update_branch function is meant to address this, but it's unused in the current code. Alternatively we could do git describe origin/{branch_name} (after the git fetch), which avoids the problems of statefullness.

I'm inclined to merge this PR now as-is and we can come back for these changes if others agree?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

So I tried the describe approach and didn't work. I'll just do checkout branch, pull, fetch tags and then describe. What do you think?

Copy link
Member

Choose a reason for hiding this comment

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

I think that's fine! I'm surprised the describe approach doesn't work though

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh I think it might be because I testing against my lighthouse repo and I've never updated my remote master, let me try again

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yep it works

@michaelsproul
Copy link
Member

bors r+

bors bot pushed a commit that referenced this pull request Jul 3, 2022
…ration test (#3303)

## Issue Addressed

Currently the execution-engine-integration test uses latest master for nethermind and geth, and right now the test fails using the latest unreleased commits.

## Proposed Changes
Fix the nethermind and geth revisions the test uses to the latest tag in each repo. This way we are not continuously testing unreleased code, which might even get reverted, and reduce the failures only to releases in each one.
Also improve error handling of the commands used to manage the git repos.

## Additional Info
na

Co-authored-by: Michael Sproul <[email protected]>
@divagant-martian
Copy link
Contributor Author

bors r-

I'm cancelling to address what you've raised

@bors
Copy link

bors bot commented Jul 3, 2022

Canceled.

@michaelsproul
Copy link
Member

It seems the latest Geth tag has some incompatibility, the failure doesn't seem related to your latest change

@divagant-martian
Copy link
Contributor Author

the selected tag was not the right one, now should work

@divagant-martian
Copy link
Contributor Author

bors r+

bors bot pushed a commit that referenced this pull request Jul 3, 2022
…ration test (#3303)

## Issue Addressed

Currently the execution-engine-integration test uses latest master for nethermind and geth, and right now the test fails using the latest unreleased commits.

## Proposed Changes
Fix the nethermind and geth revisions the test uses to the latest tag in each repo. This way we are not continuously testing unreleased code, which might even get reverted, and reduce the failures only to releases in each one.
Also improve error handling of the commands used to manage the git repos.

## Additional Info
na

Co-authored-by: Michael Sproul <[email protected]>
@bors
Copy link

bors bot commented Jul 3, 2022

Build failed:

@divagant-martian
Copy link
Contributor Author

bors retry

@michaelsproul
Copy link
Member

bors r-

@bors
Copy link

bors bot commented Jul 3, 2022

Canceled.

@michaelsproul
Copy link
Member

bors r+

bors bot pushed a commit that referenced this pull request Jul 3, 2022
…ration test (#3303)

## Issue Addressed

Currently the execution-engine-integration test uses latest master for nethermind and geth, and right now the test fails using the latest unreleased commits.

## Proposed Changes
Fix the nethermind and geth revisions the test uses to the latest tag in each repo. This way we are not continuously testing unreleased code, which might even get reverted, and reduce the failures only to releases in each one.
Also improve error handling of the commands used to manage the git repos.

## Additional Info
na

Co-authored-by: Michael Sproul <[email protected]>
@bors bors bot changed the title Use latest tags for nethermind and geth in the execution engine integration test [Merged by Bors] - Use latest tags for nethermind and geth in the execution engine integration test Jul 3, 2022
@bors bors bot closed this Jul 3, 2022
@divagant-martian divagant-martian deleted the test branch July 3, 2022 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-merge This PR is ready to merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants