Update name of Ubuntu 24.04 Docker image used as input - #669
Update name of Ubuntu 24.04 Docker image used as input#669jafingerhut wants to merge 22 commits into
Conversation
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
…ckages Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
ones that are more easily installable on Ubuntu 24.04 Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
| docker run -w /PI pi bash -c \ | ||
| 'apt-get update && apt-get install -y python3-pip && \ | ||
| python3 -m pip install ptf scapy grpcio googleapis-common-protos protobuf==3.20 && \ | ||
| 'sudo apt-get update && sudo apt-get install -y build-essential python3-dev && |
There was a problem hiding this comment.
sudo is not available in docker iirc.
Looks like this should be part of the third-party image, if it is missing?
There was a problem hiding this comment.
For the record, also okay to add it here, but likely should be in the build file.
Not when we run tests. If the tests fail, our image is incomplete
There was a problem hiding this comment.
Thanks for the advice. Right now I am looking into some failures to compile the PI code when configure is used to enable all of the optional pieces. I have compiled PI with a subset of its options enabled for years on Ubuntu 24.04 and gotten it to pass tests when linked with simple_switch_grpc and run through all of p4c's tests, for example, but apparently there is PI C++ code that does not compile at all with the default version of GCC installed by apt on Ubuntu 24.04, that I haven't ever tried to compile before now.
We are experiencing this because either (a) no one has ever tried this before and seen the failures, or (b) they have experienced them, but haven't bothered to report them.
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
|
@fruffy This should be passing all tests now. I also did these changes:
|
| strategy: | ||
| matrix: | ||
| include: | ||
| - cxx: clang++-18 |
There was a problem hiding this comment.
Can we make this generic like we do with gcc?
There was a problem hiding this comment.
Done in commit 16, passes CI tests still.
| docker run -w /PI pi bash -c \ | ||
| 'apt-get update && apt-get install -y python3-pip && \ | ||
| python3 -m pip install ptf scapy grpcio googleapis-common-protos protobuf==3.20 && \ | ||
| 'apt-get update && apt-get install -y build-essential python3-dev && |
There was a problem hiding this comment.
This should be part of the build step, not the test step. If the tests require this to pass we are shipping a broken image
| apt-get install -y --no-install-recommends $PI_DEPS $PI_RUNTIME_DEPS && \ | ||
| ./autogen.sh && \ | ||
| ./configure --enable-Werror --with-bmv2 --with-proto --with-cli --with-internal-rpc --with-sysrepo && \ | ||
| # TODO: Change --without-proto to --with-proto when we learn how |
There was a problem hiding this comment.
What is the actual error here? Maybe it is a trivial fix
There was a problem hiding this comment.
You can see the errors in the logs of this similar PR, which I created in parallel to try out some variations on this one.
There was a problem hiding this comment.
I have since found fairly small changes to the C++ code to keep the proto option enabled during PI conigure step. The changes are in the PR #670, which I suspect may replace this one soon. I plan to make a few more commits to #670 soon to try to move the installation of Python packages into the build step rather than the test step, as you commented on for this PR.
instead of picking a particular version number Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
…lures Signed-off-by: Andy Fingerhut <andy_fingerhut@alum.wustl.edu>
|
Closing this PR, as I recommend reviewing PR #670 instead. |
No description provided.