You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2024-06-28] [HOLD for payment 2024-06-13] Investigate workflow job failing on main: e2ePerformanceTests / Run E2E tests in AWS device farm #42987
🛠️ A recent merge appears to have caused a failure in the job named e2ePerformanceTests / Run E2E tests in AWS device farm.
This issue has been automatically created and labeled with Workflow Failure for investigation.
The PR in question changed 1 boolean condition which affects some edge case whether ProfilePage shows up or NotFound page.
I highly doubt it affected performance. It's probably just a false-positive flaky test.
changed the title [-]Investigate workflow job failing on main: e2ePerformanceTests / Run E2E tests in AWS device farm[/-][+][HOLD for payment 2024-06-13] Investigate workflow job failing on main: e2ePerformanceTests / Run E2E tests in AWS device farm[/+]on Jun 6, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.79-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
changed the title [-][HOLD for payment 2024-06-13] Investigate workflow job failing on main: e2ePerformanceTests / Run E2E tests in AWS device farm[/-][+][HOLD for payment 2024-06-28] [HOLD for payment 2024-06-13] Investigate workflow job failing on main: e2ePerformanceTests / Run E2E tests in AWS device farm[/+]on Jun 21, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.85-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
Kicu commentedon Jun 3, 2024
The PR in question changed 1 boolean condition which affects some edge case whether ProfilePage shows up or NotFound page.
I highly doubt it affected performance. It's probably just a false-positive flaky test.
kirillzyusko commentedon Jun 3, 2024
@Kicu yeah, you are right - these failures are not related to these changes.
I already foudn a root cause and will submit a fix soon 🤞
[-]Investigate workflow job failing on main: e2ePerformanceTests / Run E2E tests in AWS device farm[/-][+][HOLD for payment 2024-06-13] Investigate workflow job failing on main: e2ePerformanceTests / Run E2E tests in AWS device farm[/+]melvin-bot commentedon Jun 6, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jun 6, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.79-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-06-13. 🎊
[-][HOLD for payment 2024-06-13] Investigate workflow job failing on main: e2ePerformanceTests / Run E2E tests in AWS device farm[/-][+][HOLD for payment 2024-06-28] [HOLD for payment 2024-06-13] Investigate workflow job failing on main: e2ePerformanceTests / Run E2E tests in AWS device farm[/+]melvin-bot commentedon Jun 21, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jun 21, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.85-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-06-28. 🎊