-
Notifications
You must be signed in to change notification settings - Fork 817
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
Tests update: Use require package in fleets package #1685
Tests update: Use require package in fleets package #1685
Conversation
Build Failed 😱 Build Id: d6141283-019e-4e41-9b2a-0f613fc23143 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
63acd22
to
108149f
Compare
Build Failed 😱 Build Id: 3a818873-71a0-4428-a957-1d2140a17951 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Failed 😱 Build Id: c7b8b6fe-a487-4139-98ac-874309647f9d To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
935d333
to
f692db8
Compare
Build Succeeded 👏 Build Id: afea8c59-1e02-4ca1-ace6-ddc0e30ee8a9 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
I question if we should be replacing all asserts with require? Just thinking of other work that might be more valuable long term. Or should we just replace the instances where we are doing variations of |
One benefit which I see from using assert is that it will show ALL failed cases if they exist at once. For example:
This code will output 2 errors for each assert at once which can be useful to see all possible failed test cases. |
100% agree 👍 |
f692db8
to
7befbf0
Compare
Build Failed 😱 Build Id: f13aebe0-b097-4048-8447-de09ca3373f1 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
7befbf0
to
a6c1db2
Compare
Build Failed 😱 Build Id: 74de68e2-12de-4ab5-b8e1-ed0c4b6f47b0 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Does it make sense to close this PR? Since it looks like it won't be merged in it's current state? (sorry @akremsa !) |
@markmandel do you mean failed builds? Otherwise, this PR is perfectly fine, no? |
Let me come at this question another way - is all the places you've updated in this PR places where we want to abort execution of the test at the time of failure? Maybe I misunderstood where we ended up. |
"is all the places you've updated in this PR places where we want to abort execution of the test at the time of failure" |
Ah! Got it. I will review this with that in mind. In which case, ignore my previous comment! |
Build Succeeded 👏 Build Id: 670f8584-a6a7-4ead-8dab-429b01260000 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
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.
LGTM!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: akremsa, markmandel The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
Build Failed 😱 Build Id: e2d881a9-f311-485d-aaaf-dd61fbe735dd To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
|
Build Succeeded 👏 Build Id: b8bd80d1-a50f-494c-a3ca-e2af7424cf94 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
What type of PR is this?
What this PR does / Why we need it:
Use require package to abort test in order to avoid nil pointer exceptions.