Skip to content
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

Build and Test on Github fails at build-image-pr #17306

Closed
qwertiko opened this issue Apr 15, 2020 · 2 comments
Closed

Build and Test on Github fails at build-image-pr #17306

qwertiko opened this issue Apr 15, 2020 · 2 comments

Comments

@qwertiko
Copy link
Contributor

Description:

build-image-pr on github fails repeatedly at "Build Docker image for PRs" with error:
denied: Resource not accessible by integration
##[error]Process completed with exit code 1.

Steps to reproduce:

  1. Create new pull request
  2. Let the auto build and test suite run

Expected behavior:

The integration test finishes successfully

Actual behavior:

The integration test fails with access failure.

Relevant logs:

Except from build-image-pr at step "Build Docker image for PRs":

Step 9/10 : EXPOSE 3000
---> Running in 72b4c20236c1
Removing intermediate container 72b4c20236c1
---> e417fffc4b50
Step 10/10 : CMD ["node", "main.js"]
---> Running in 515050a66bf0
Removing intermediate container 515050a66bf0
---> 3dc481828a45
Successfully built 3dc481828a45
Successfully tagged docker.pkg.github.com/rocketchat/rocket.chat/rocket.chat:pr-16430
The push refers to repository [docker.pkg.github.com/rocketchat/rocket.chat/rocket.chat]
a7acdaba9313: Preparing
2c4edf051dec: Preparing
430c0c0c04ea: Preparing
a60dd2539360: Preparing
30e8a2fe960c: Preparing
2c995a2087c1: Preparing
2c995a2087c1: Waiting
a60dd2539360: Layer already exists
430c0c0c04ea: Layer already exists
30e8a2fe960c: Layer already exists
2c995a2087c1: Layer already exists
denied: Resource not accessible by integration
##[error]Process completed with exit code 1.

@github-actions
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stat: stale Stale issues will be automatically closed if no activity label Jun 19, 2020
@sampaiodiego
Copy link
Member

fixed by #17370

@sampaiodiego sampaiodiego removed the stat: stale Stale issues will be automatically closed if no activity label Jun 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants