-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
docker: builder fixups #7890
docker: builder fixups #7890
Conversation
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.
LGTM
Outdated results 💚Basic BGPD CI results: SUCCESS, 0 tests failed
For details, please contact louberger |
Continuous Integration Result: FAILEDContinuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedTopo tests part 3 on Ubuntu 18.04 arm8: Failed (click for details)Topo tests part 3 on Ubuntu 18.04 arm8: No useful log foundSuccessful on other platforms/tests
Warnings Generated during build:Debian 10 amd64 build: Successful with additional warningsDebian Package lintian failed for Debian 10 amd64 build:
|
ci:rerun |
Continuous Integration Result: FAILEDContinuous Integration Result: FAILEDSee below for issues. This is a comment from an automated CI system. Get source / Pull Request: SuccessfulBuilding Stage: SuccessfulBasic Tests: FailedTopo tests part 3 on Ubuntu 18.04 arm8: Failed (click for details)Topo tests part 3 on Ubuntu 18.04 arm8: No useful log foundTopo tests part 2 on Ubuntu 18.04 amd64: Failed (click for details)Topology Test Results are at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-TP2U1804AMD64-16609/test Topology Tests failed for Topo tests part 2 on Ubuntu 18.04 amd64:
see full log at https://ci1.netdef.org/browse/FRR-FRRPULLREQ-16609/artifact/TP2U1804AMD64/ErrorLog/log_topotests.txt Successful on other platforms/tests
Warnings Generated during build:Debian 10 amd64 build: Successful with additional warningsDebian Package lintian failed for Debian 10 amd64 build:
|
@wesleycoakley please rebase to the latest master, lots have been fixed regarding CI. |
Building with alpine:edge caused some weirdness with our build scripts, switching to the stable branch seems to have aleviated this. We can also ditch the "edge" repositories as the main and community repositories provide all packages we need Signed-off-by: Wesley Coakley <wcoakley@nvidia.com>
Bump libyang version in centos containers to 1.0.184 and (1) change "PowerTools" repository to "powertools" to accomodate CentOS Stream changes (1) https://bugs.centos.org/view.php?id=17920 Signed-off-by: Wesley Coakley <wcoakley@nvidia.com>
bba8e92
to
5fc9775
Compare
💚 Basic BGPD CI results: SUCCESS, 0 tests failedResults table
For details, please contact louberger |
Continuous Integration Result: SUCCESSFULCongratulations, this patch passed basic tests Tested-by: NetDEF / OpenSourceRouting.org CI System CI System Testrun URL: https://ci1.netdef.org/browse/FRR-FRRPULLREQ-16636/ This is a comment from an automated CI system. Warnings Generated during build:Debian 10 amd64 build: Successful with additional warningsDebian Package lintian failed for Debian 10 amd64 build:
|
Just some housekeeping for our Docker containers, fixing issues I found while building our Docker containers for use in network simulation:
alpine:latest
instead ofalpine:edge
tag for Alpine builds, as edge was causing automake failuresedge
package repository in Alpine builder for above reason (they have had libyang 1.0.84 for some time in the community branch so use that)PowerTools
repository was recently renamed topowertools
so use that instead because that made the whole builder failI've verified that the containers now build on all my machines, albeit these are all Gentoo boxes 🙂