-
Notifications
You must be signed in to change notification settings - Fork 826
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
CI: Wait for tests step before sdk-conformance #1808
Conversation
/lint |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Build Failed 😱 Build Id: ec6247fe-fe6a-4013-9b68-02030c22e808 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Too many simultaneous E2E tests but conformance was OK:
And from another test run:
|
Build Succeeded 👏 Build Id: 381c1160-2671-4776-b414-c9cf43a30b04 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:
|
b1537c4
to
b8e547f
Compare
Both this test would trigger building with `go run` or `npm run` in parallel on the same volume mounts.
b8e547f
to
5730984
Compare
Build Succeeded 👏 Build Id: 766000f9-c222-4a5e-a778-5622786c8f3b 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:
|
Build Succeeded 👏 Build Id: d15a6038-cdb4-4b8e-8cde-eefa6ab814b0 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:
|
This is looking like it's solving the issue? Although it does look like it pushes the CI time to completion from around 18 minutes to around 30 - which is a big jump (that being said, we're probably at that already with retries, so 🤷) Run it a few more times, and if it keeps passing, I say let's merge it. WDYT? |
Well, yes, longest running time is bad, we can fix this side effect somehow with caching. We can see SDK conformance would not come up at a later time, if it would be as frequent as now, we can remove this |
Build Succeeded 👏 Build Id: e802f517-5d92-4eb4-8526-55cf6522cd79 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.
Hasn't failed yet!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aLekSer, 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 Succeeded 👏 Build Id: 6072076c-bcca-4d2f-a015-7c179efb4624 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:
|
Both this test would trigger building with `go run` or `npm run` in parallel on the same volume mounts. Co-authored-by: Mark Mandel <markmandel@google.com>
Both these steps would trigger building with
go run
ornpm run
inparallel on the same directories.
What type of PR is this?
/kind bug
What this PR does / Why we need it:
CI is fluctuating and fails too frequently.
Which issue(s) this PR fixes:
Work on #1779
Special notes for your reviewer: