I scheduled 6 ci.d.n runs on s390x, and there was 1 pass: https://ci.debian.net/packages/g/golang-github-prometheus-community-pro-bing/unstable/s390x/73991072/
and 5 fail: https://ci.debian.net/packages/g/golang-github-prometheus-community-pro-bing/unstable/s390x/73991069/ https://ci.debian.net/packages/g/golang-github-prometheus-community-pro-bing/unstable/s390x/73991071/ https://ci.debian.net/packages/g/golang-github-prometheus-community-pro-bing/unstable/s390x/73991070/ https://ci.debian.net/packages/g/golang-github-prometheus-community-pro-bing/unstable/s390x/73991073/ I think we should package latest upstream, and if that still trigger the problem, make an upstream bug report and temporarily disable the self-test on s390x in Debian. Any objections or other considerations? We currently ship 0.8.0 and latest upstream is 0.9.1. The reverse build dependencies are: librespeed-cli prometheus-smokeping-prober riseup-vpn Reading their go.mod files: Latest librespeed-cli in Debian (1.0.13) uses pro-bing 0.8.0, and latest upstream git also uses 0.8.0. Latest prometheus-smokeping-prober in Debian (0.11.0) uses pro-bing 0.8.0, latest upstream (0.12.0) uses pro-bing 0.9.0. Latest riseup-vpn in Debian (0.24.10) uses pro-bing 0.4.0 although only indirectly (so not sure why pro-bing is a direct build-depends). Latest upstream git uses (also indirectly) pro-bing 0.7.0. /Simon
signature.asc
Description: PGP signature
