Skip to content

Added e2e test to reproduce issue #340 #397

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

Merged
merged 3 commits into from
Jun 1, 2023

Conversation

z103cb
Copy link
Contributor

@z103cb z103cb commented May 29, 2023

Minor fixes in the e2e script.
@z103cb z103cb self-assigned this May 29, 2023
@z103cb z103cb requested review from asm582, dmatch01 and KPostOffice May 29, 2023 12:26
@z103cb
Copy link
Contributor Author

z103cb commented May 29, 2023

@KPostOffice can you review the setup in the e2e test let me know if it matches what you observed when you filed #340?

@KPostOffice, @metalcycling and @asm582 I can't seem to reproduce issue #340 after merging #367. I would appreciate some help in determining if the issue is still present. I think that the e2e test additions do have value even if we can't reproduce the original issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

2 participants