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

Flake: hack/build-images.sh fails with "stat examples/gitserver/bin/gitserver: no such file or directory" #17684

Closed
tnozicka opened this issue Dec 8, 2017 · 8 comments
Assignees
Labels
component/internal-tools kind/bug Categorizes issue or PR as related to a bug. priority/P1

Comments

@tnozicka
Copy link
Contributor

tnozicka commented Dec 8, 2017

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17620/test_pull_request_origin_extended_conformance_install/3776/

[WARNING] Retrying image build for openshift/origin-gitserver:latest, attempt 1...
[openshift/origin-gitserver] --> FROM openshift/origin
[openshift/origin-gitserver] --> COPY bin/gitserver /usr/bin/gitserver
[openshift/origin-gitserver] stat examples/gitserver/bin/gitserver: no such file or directory
@tnozicka tnozicka added kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1 labels Dec 8, 2017
@php-coder php-coder changed the title Flake: hack/build-images.sh:56: return "${result}" exited with status 1. Flake: hack/build-images.sh fails with "stat examples/gitserver/bin/gitserver: no such file or directory" Dec 8, 2017
@php-coder
Copy link
Contributor

Hm.. it should be fixed already (#17345).

CC @jupierce

@tnozicka
Copy link
Contributor Author

tnozicka commented Dec 8, 2017

this PR was for release-3.7 branch and it doesn't have #17373

@pweil- pweil- added component/internal-tools kind/bug Categorizes issue or PR as related to a bug. and removed kind/test-flake Categorizes issue or PR as related to test flakes. labels Dec 11, 2017
@jupierce
Copy link
Contributor

@tnozicka The release-3.7 branch is no longer pulled into OCP 3.7 and should not be targeted by PRs. You will need to PR against ose/enterprise-3.7 .

@tnozicka
Copy link
Contributor Author

@jupierce what if I want to fix origin as well, why shouldn't I target release-3.7? 3.7 is our latest stable release in upstream.

I am not sure why we don't auto pull stuff from origin release-3.7 anymore but I'll send it manually there too.

@jupierce
Copy link
Contributor

@tnozicka We just don't offer long term support in these branches.

@tnozicka
Copy link
Contributor Author

If previous releases in origin are of any guidance we used to release x.x.1 at least. I went though the history and we've released (1.1.6, 1.2.2, 1.3.3, 1.4.1, 1.5.1, 3.6.1).

@smarterclayton is 3.7 in origin really dead? Are we sure there won't be 3.7.1? For one I know that 3.7.0 oc cluster up is completely broken on some platforms (#17638)

How can we mark 3.7 as not supported without having a newer release?

@smarterclayton
Copy link
Contributor

The branch should be fixed, but gitserver should be removed.

@smarterclayton
Copy link
Contributor

smarterclayton commented Dec 21, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/internal-tools kind/bug Categorizes issue or PR as related to a bug. priority/P1
Projects
None yet
Development

No branches or pull requests

5 participants