Revert parallel Docker builds#12246
Conversation
5cf722b to
6775123
Compare
|
@smarterclayton @bparees the linked issue suggests reversion. I don't see a followup that fixes the problem. Any reason not to merge this? [test] |
|
Generated with: $ git revert f8b5dd6fe2b1e1e584e1f790435bcf9a98bf3eb3 -m 1
$ git revert b61cf87413a73268ff35fdeec0bade6b2e6eb61e -m 1 |
|
Evaluated for origin test up to 6775123 |
|
continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/12332/) (Base Commit: fb0bbde) |
|
[merge] |
|
@smarterclayton @bparees tagged for merge. If there's another fix, please link it when you remove the tag. |
|
continuous-integration/openshift-jenkins/merge Waiting: You are in the build queue at position: 6 |
|
Evaluated for origin merge up to 6775123 |
|
I merged yesterday. |
|
#12229 was the revert of parallelism |
|
Wow that's incredibly difficult to determine. Cool. |
|
@smarterclayton we're seeing router-related issues like: #11644 (comment) What's going on? |
|
Probably unrelated, positive it's not related to that PR?
On Dec 13, 2016, at 1:00 PM, Steve Kuznetsov <notifications@github.com> wrote:
@smarterclayton <https://github.com/smarterclayton> we're seeing
router-related issues like: #11644 (comment)
<#11644 (comment)>
What's going on?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12246 (comment)>,
or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABG_p4kjOf7kWtCpM-plyr2-C0QjaPFbks5rHt1BgaJpZM4LL3IH>
.
|
|
Not entirely sure, I had some people ask me about the router flake this morning but it looks like they all happened late yesterday. If only we had some metrics ... |
This reverts #12218 and #12229 to address #12236.
@deads2k PTAL