Builds for globus-gridmap-verify-myproxy-callout in Ubuntu Noble

148 of 48 results
[FULLYBUILT] s390x build of globus-gridmap-verify-myproxy-callout 3.2-4 in ubuntu noble PROPOSED
Build started on bos01-s390x-008 and finished taking 2 minutes — see the log
[FULLYBUILT] s390x build of globus-gridmap-verify-myproxy-callout 3.2-4 in ubuntu noble PROPOSED
Build started on bos01-s390x-008 and finished taking 2 minutes — see the log
[FULLYBUILT] riscv64 build of globus-gridmap-verify-myproxy-callout 3.2-4 in ubuntu noble PROPOSED
Build started on bos03-riscv64-089 and finished taking 16 minutes — see the log
[FULLYBUILT] riscv64 build of globus-gridmap-verify-myproxy-callout 3.2-4 in ubuntu noble PROPOSED
Build started on bos03-riscv64-089 and finished taking 16 minutes — see the log
[FULLYBUILT] ppc64el build of globus-gridmap-verify-myproxy-callout 3.2-4 in ubuntu noble PROPOSED
Build started on bos02-ppc64el-018 and finished taking 3 minutes — see the log
[FULLYBUILT] ppc64el build of globus-gridmap-verify-myproxy-callout 3.2-4 in ubuntu noble PROPOSED
Build started on bos02-ppc64el-018 and finished taking 3 minutes — see the log
[FULLYBUILT] armhf build of globus-gridmap-verify-myproxy-callout 3.2-4 in ubuntu noble PROPOSED
Build started on bos02-arm64-064 and finished taking 3 minutes — see the log
[FULLYBUILT] armhf build of globus-gridmap-verify-myproxy-callout 3.2-4 in ubuntu noble PROPOSED
Build started on bos02-arm64-064 and finished taking 3 minutes — see the log
[FULLYBUILT] arm64 build of globus-gridmap-verify-myproxy-callout 3.2-4 in ubuntu noble PROPOSED
Build started on bos02-arm64-070 and finished taking 4 minutes — see the log
[FULLYBUILT] arm64 build of globus-gridmap-verify-myproxy-callout 3.2-4 in ubuntu noble PROPOSED
Build started on bos02-arm64-070 and finished taking 4 minutes — see the log
[FULLYBUILT] amd64 build of globus-gridmap-verify-myproxy-callout 3.2-4 in ubuntu noble PROPOSED
Build started on lcy02-amd64-034 and finished taking 1 minute — see the log
[FULLYBUILT] amd64 build of globus-gridmap-verify-myproxy-callout 3.2-4 in ubuntu noble PROPOSED
Build started on lcy02-amd64-034 and finished taking 1 minute — see the log
[FULLYBUILT] s390x build of globus-gridmap-verify-myproxy-callout 3.2-3build2 in ubuntu noble PROPOSED
Build started on bos01-s390x-018 and finished taking 5 minutes — see the log
[FULLYBUILT] s390x build of globus-gridmap-verify-myproxy-callout 3.2-3build2 in ubuntu noble PROPOSED
Build started on bos01-s390x-018 and finished taking 5 minutes — see the log
[FULLYBUILT] riscv64 build of globus-gridmap-verify-myproxy-callout 3.2-3build2 in ubuntu noble PROPOSED
Build started on bos03-riscv64-090 and finished taking 21 minutes — see the log
[FULLYBUILT] riscv64 build of globus-gridmap-verify-myproxy-callout 3.2-3build2 in ubuntu noble PROPOSED
Build started on bos03-riscv64-090 and finished taking 21 minutes — see the log
[FULLYBUILT] ppc64el build of globus-gridmap-verify-myproxy-callout 3.2-3build2 in ubuntu noble PROPOSED
Build started on bos01-ppc64el-012 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of globus-gridmap-verify-myproxy-callout 3.2-3build2 in ubuntu noble PROPOSED
Build started on bos01-ppc64el-012 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of globus-gridmap-verify-myproxy-callout 3.2-3build2 in ubuntu noble PROPOSED
Build started on bos03-arm64-038 and finished taking 7 minutes — see the log
[FULLYBUILT] armhf build of globus-gridmap-verify-myproxy-callout 3.2-3build2 in ubuntu noble PROPOSED
Build started on bos03-arm64-038 and finished taking 7 minutes — see the log
[FULLYBUILT] arm64 build of globus-gridmap-verify-myproxy-callout 3.2-3build2 in ubuntu noble PROPOSED
Build started on bos02-arm64-033 and finished taking 7 minutes — see the log
[FULLYBUILT] arm64 build of globus-gridmap-verify-myproxy-callout 3.2-3build2 in ubuntu noble PROPOSED
Build started on bos02-arm64-033 and finished taking 7 minutes — see the log
[FULLYBUILT] amd64 build of globus-gridmap-verify-myproxy-callout 3.2-3build2 in ubuntu noble PROPOSED
Build started on lcy02-amd64-094 and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of globus-gridmap-verify-myproxy-callout 3.2-3build2 in ubuntu noble PROPOSED
Build started on lcy02-amd64-094 and finished taking 3 minutes — see the log
[FULLYBUILT] s390x build of globus-gridmap-verify-myproxy-callout 3.2-3build1 in ubuntu noble PROPOSED
Build started on bos02-s390x-014 and finished taking 3 minutes — see the log
[FULLYBUILT] s390x build of globus-gridmap-verify-myproxy-callout 3.2-3build1 in ubuntu noble PROPOSED
Build started on bos02-s390x-014 and finished taking 3 minutes — see the log
[FULLYBUILT] riscv64 build of globus-gridmap-verify-myproxy-callout 3.2-3build1 in ubuntu noble PROPOSED
Build started on bos03-riscv64-021 and finished taking 19 minutes — see the log
[FULLYBUILT] riscv64 build of globus-gridmap-verify-myproxy-callout 3.2-3build1 in ubuntu noble PROPOSED
Build started on bos03-riscv64-021 and finished taking 19 minutes — see the log
[FULLYBUILT] ppc64el build of globus-gridmap-verify-myproxy-callout 3.2-3build1 in ubuntu noble PROPOSED
Build started on bos02-ppc64el-023 and finished taking 3 minutes — see the log
[FULLYBUILT] ppc64el build of globus-gridmap-verify-myproxy-callout 3.2-3build1 in ubuntu noble PROPOSED
Build started on bos02-ppc64el-023 and finished taking 3 minutes — see the log
[FULLYBUILT] armhf build of globus-gridmap-verify-myproxy-callout 3.2-3build1 in ubuntu noble PROPOSED
Build started on bos02-arm64-076 and finished taking 6 minutes — see the log
[FULLYBUILT] armhf build of globus-gridmap-verify-myproxy-callout 3.2-3build1 in ubuntu noble PROPOSED
Build started on bos02-arm64-076 and finished taking 6 minutes — see the log
[FULLYBUILT] arm64 build of globus-gridmap-verify-myproxy-callout 3.2-3build1 in ubuntu noble PROPOSED
Build started on bos02-arm64-053 and finished taking 5 minutes — see the log
[FULLYBUILT] arm64 build of globus-gridmap-verify-myproxy-callout 3.2-3build1 in ubuntu noble PROPOSED
Build started on bos02-arm64-053 and finished taking 5 minutes — see the log
[FULLYBUILT] amd64 build of globus-gridmap-verify-myproxy-callout 3.2-3build1 in ubuntu noble PROPOSED
Build started on lcy02-amd64-080 and finished taking 3 minutes — see the log
[FULLYBUILT] amd64 build of globus-gridmap-verify-myproxy-callout 3.2-3build1 in ubuntu noble PROPOSED
Build started on lcy02-amd64-080 and finished taking 3 minutes — see the log
[FULLYBUILT] s390x build of globus-gridmap-verify-myproxy-callout 3.2-3 in ubuntu kinetic PROPOSED
Build started on bos02-s390x-017 and finished taking 1 minute — see the log
[FULLYBUILT] s390x build of globus-gridmap-verify-myproxy-callout 3.2-3 in ubuntu kinetic PROPOSED
Build started on bos02-s390x-017 and finished taking 1 minute — see the log
[FULLYBUILT] riscv64 build of globus-gridmap-verify-myproxy-callout 3.2-3 in ubuntu kinetic PROPOSED
Build started on riscv64-qemu-lgw01-066 and finished taking 27 minutes — see the log
[FULLYBUILT] riscv64 build of globus-gridmap-verify-myproxy-callout 3.2-3 in ubuntu kinetic PROPOSED
Build started on riscv64-qemu-lgw01-066 and finished taking 27 minutes — see the log
[FULLYBUILT] ppc64el build of globus-gridmap-verify-myproxy-callout 3.2-3 in ubuntu kinetic PROPOSED
Build started on bos02-ppc64el-006 and finished taking 2 minutes — see the log
[FULLYBUILT] ppc64el build of globus-gridmap-verify-myproxy-callout 3.2-3 in ubuntu kinetic PROPOSED
Build started on bos02-ppc64el-006 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of globus-gridmap-verify-myproxy-callout 3.2-3 in ubuntu kinetic PROPOSED
Build started on bos02-arm64-026 and finished taking 2 minutes — see the log
[FULLYBUILT] armhf build of globus-gridmap-verify-myproxy-callout 3.2-3 in ubuntu kinetic PROPOSED
Build started on bos02-arm64-026 and finished taking 2 minutes — see the log
[FULLYBUILT] arm64 build of globus-gridmap-verify-myproxy-callout 3.2-3 in ubuntu kinetic PROPOSED
Build started on bos02-arm64-054 and finished taking 2 minutes — see the log
[FULLYBUILT] arm64 build of globus-gridmap-verify-myproxy-callout 3.2-3 in ubuntu kinetic PROPOSED
Build started on bos02-arm64-054 and finished taking 2 minutes — see the log
[FULLYBUILT] amd64 build of globus-gridmap-verify-myproxy-callout 3.2-3 in ubuntu kinetic PROPOSED
Build started on lcy02-amd64-002 and finished taking 2 minutes — see the log
[FULLYBUILT] amd64 build of globus-gridmap-verify-myproxy-callout 3.2-3 in ubuntu kinetic PROPOSED
Build started on lcy02-amd64-002 and finished taking 2 minutes — see the log
148 of 48 results