Silence "using cache" to ensure -q is fully quiet

[tylarb]

• Add a helper function inside of (s *StageExecutor) Execute() to
  handle "using cache" messages

Signed-off-by: Tyler Ramer [email protected]

---

Addresses #1897

[rh-atomic-bot]

Can one of the admins verify this patch?
I understand the following commands:

• bot, add author to whitelist
• bot, test pull request
• bot, test pull request once

[TomSweeneyRedHat]

bot, add author to whitelist

[TomSweeneyRedHat]

Thanks for the PR @tylarb . First blush and it LGTM, I do want to give it a quick test run in the morn. Thanks!

[TomSweeneyRedHat]

@tylarb we require that PR's be signed. Could you git commit --amend -s and repush your PR please?

[TomSweeneyRedHat]

And FWIW, I tested this morning and it looks good. Thanks a bunch and nice spot and fix!

[tylarb]

@TomSweeneyRedHat re-pushed. Our pairing signatures look a little different. Thanks much!

[TomSweeneyRedHat]

@tylarb thanks! Yeah when I looked last night at your sig in the description, I thought you were all set. Gotta luv computers.

[TomSweeneyRedHat]

@nalind, @vrothberg, @rhatdan PTAL. Happy green test buttons.

[rhatdan]

Thanks @tylarb
@rh-atomic-bot r+

[rh-atomic-bot]

📌 Commit e87aa86 has been approved by rhatdan

[rh-atomic-bot]

⌛ Testing commit e87aa86 with merge 974bd98...

[rh-atomic-bot]

☀️ Test successful - status-papr, status-travis
Approved by: rhatdan
Pushing 974bd98 to master...

[rh-atomic-bot]

👀 Test was successful, but fast-forwarding failed: 422 Update is not a fast forward

[tylarb]

Test was successful, but fast-forwarding failed: 422 Update is not a fast forward

Is this something I need to fix?

[TomSweeneyRedHat]

@tylarb no nothing for you to tweak now. This is homu giving us more pain than it's sometimes worth, it sometimes has random flakes like this. I've tried restarting. If it's still not happy, we might ask you to rebase and push again tomorrow as that sometimes clears things with homu.

[rh-atomic-bot]

☀️ Test successful - status-papr, status-travis
Approved by: rhatdan
Pushing 974bd98 to master...

[rh-atomic-bot]

👀 Test was successful, but fast-forwarding failed: 422 Update is not a fast forward

[TomSweeneyRedHat]

@jlebon or @cevich, do you know what this homu failure means and better yet, what to do to fix it?

Test was successful, but fast-forwarding failed: 422 Update is not a fast forward

[jlebon]

Hmm, I think what happened is that by the time it was done testing and ready to push to master, it found that master already had a new commit on top (#1926). The way Homu works, it really wants to be in control of all merges.

Anyway, this repo should be hooked to Prow now. So /lgtm should work. Otherwise, rebasing should work too.

[TomSweeneyRedHat]

/lgtm

[TomSweeneyRedHat]

@tylarb looks like the /lgtm didn't work, can you try rebasing and repushing again please?

[tylarb]

Rebased... but now tests are failing... Looks like a docker registry issue:

# error creating build container: Error initializing source docker://registry.centos.org/centos/centos:centos7: pinging docker registry returned: error pinging registry registry.centos.org, response code 500 (Internal Server Error)

[TomSweeneyRedHat]

I've restarted the jobs and crossed my fingers.

[rhatdan]

@rh-atomic-bot r+

[rh-atomic-bot]

📌 Commit 83b881e has been approved by rhatdan