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

Cristi/schedule e2e tests #5161

Merged
merged 4 commits into from
Oct 17, 2023
Merged

Conversation

CristiCanizales
Copy link
Contributor

@CristiCanizales CristiCanizales commented Oct 17, 2023

What does this PR do?

  • Adds condition to if to include runs triggered with "schedule"

Functionality Before

  • Tests being skipped in scheduled runs because if condition was missing

Functionality After

  • Tests finally running..

These runs were triggered on my fork with a workflow like the one I fixed in this PR:

They're failing because I don't have the right setup on my fork (secrets and all that) but they're being run automatically as scheduled

[skip-validate-pr]

Copy link
Contributor

@daphne-sfdc daphne-sfdc left a comment

Choose a reason for hiding this comment

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

Approved! 🎉 Thanks for getting the scheduling to work!

@diyer
Copy link
Collaborator

diyer commented Oct 17, 2023

will these be run as part of nightly runs? if yes, do we get any notifications for these runs on email or slack?

@CristiCanizales
Copy link
Contributor Author

@diyer Yes, the tests would run nightly. Regarding the notifications, right now we don't get any. Gordon was going to create a WI to address that and some other e2e details to consider.

@CristiCanizales CristiCanizales merged commit 7bc2ae7 into develop Oct 17, 2023
15 checks passed
@CristiCanizales CristiCanizales deleted the cristi/schedule-e2e-tests branch October 17, 2023 23:31
@diyer
Copy link
Collaborator

diyer commented Oct 18, 2023

@CristiCanizales qq: why do you use [skip-validate-pr] on this PR ?

@CristiCanizales
Copy link
Contributor Author

@diyer We use that when the work/change was simple enough to not require a WI

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