Both projects have a build matrix testing with several different options on several platforms, including Linux on AMD64, ppc64le, s390x, and Arm64, as well as macOS on AMD64.
The build script in our .travis.yml file doesn’t need to run for Coverity builds, so it beings with
- if [ "$COVERITY_SCAN_BRANCH" = 1 ]; then exit 0; fi
The coverity_scan branch builds on Linux/AMD64 and macOS/AMD64 are succeeding (most of them do nothing, because our Coverity script stops them early; we only need one cell of the matrix to do a Coverity build). However all the non-AMD64 Linux builds terminate with “No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.”
I did a test in which I added
- if [ "$COVERITY_SCAN_BRANCH" = 0 ]; then exit 0; fi
to libpcap’s script; the Linux/AMD64 and macOS/AMD64 master branch builds succeeded (doing nothing, as would be expected), and the ppc64le and s390x Linux builds failed (I cancelled the build before the Arm64 builds were run). See the build at Travis CI - Test and Deploy Your Code with Confidence.
Those builds do not fail without that “exit 0”, as per, for example, the build at Travis CI - Test and Deploy Your Code with Confidence.
Is there something we’re doing wrong, or is this a bug in the non-AMD64 Linux build infrastructure?