-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
chore: fix component tests in contributor flow #27883
Changes from all commits
0220a06
76f8319
0cb711f
4adb2fd
8663014
22c407e
5105e9b
9a83855
9a96dfe
df4f828
37150e5
fcf6993
f3ed7e8
77406bc
d8e1d15
b092358
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1342,11 +1342,13 @@ export default { | |
const replacePreviousAttemptWith = (test) => { | ||
const prevAttempt = _testsById[test.id] | ||
|
||
const prevAttempts = prevAttempt.prevAttempts || [] | ||
const prevAttempts = prevAttempt?.prevAttempts || [] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. out of curiousity, why did you need to touch this code? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this code was throwing errors in the app component tests job for some reason - see the link to the failure in the PR description. This is what fixes those tests in the contributor workflow There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Weird. Are those component tests retrying? I'm just trying to figure out why that would happen because there should be a previous attempt here if the currentRetry is 1 or more. I'm more so concerned there is some time of regression here, but I have no idea why this would be specifically on contributor PRs. any idea? I'm also OK with patching this after we get builds working it isn't a must to figure out right now imo |
||
|
||
const newPrevAttempts = prevAttempts.concat([prevAttempt]) | ||
const newPrevAttempts = prevAttempt ? prevAttempts.concat([prevAttempt]) : prevAttempts | ||
|
||
delete prevAttempt.prevAttempts | ||
if (prevAttempt) { | ||
delete prevAttempt.prevAttempts | ||
} | ||
|
||
test.prevAttempts = newPrevAttempts | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can probably remove even more of these since the error is fixed now - most of them were excluded because of this issue I believe. I want to do that in a different PR though, since we can't test the contributor workflow until it's merged into develop