Branch: origin/master Mesos » Mesos-Buildbot - Build # 270 - Still Failing:
Check console output at https://ci-builds.apache.org/job/Mesos/job/Mesos-Buildbot/270/ to view the results. 7 tests failed. FAILED: DockerFetcherPluginTest.INTERNET_CURL_FetchBlob Error Message: /tmp/SRC/src/tests/uri_fetcher_tests.cpp:355 (fetcher.get()->fetch(uri, dir)).failure(): Failed to perform 'curl' for 'https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/a3/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4/data?verify=1713573512-iL%2BJaZzUj8g00%2BIjMwkcGX9nXZ0%3D': curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. Stack Trace: /tmp/SRC/src/tests/uri_fetcher_tests.cpp:355 (fetcher.get()->fetch(uri, dir)).failure(): Failed to perform 'curl' for 'https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/a3/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4/data?verify=1713573512-iL%2BJaZzUj8g00%2BIjMwkcGX9nXZ0%3D': curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. FAILED: DockerFetcherPluginTest.INTERNET_CURL_FetchBlob Error Message: ../../../src/tests/uri_fetcher_tests.cpp:355 (fetcher.get()->fetch(uri, dir)).failure(): Failed to perform 'curl' for 'https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/a3/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4/data?verify=1713575817-erkN0ZJ2X%2FfDQkbYK2SEWkNyVzQ%3D': curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. Stack Trace: ../../../src/tests/uri_fetcher_tests.cpp:355 (fetcher.get()->fetch(uri, dir)).failure(): Failed to perform 'curl' for 'https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/a3/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4/data?verify=1713575817-erkN0ZJ2X%2FfDQkbYK2SEWkNyVzQ%3D': curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. FAILED: ReservationEndpointsTest.LabeledResources Error Message: ../../src/tests/reservation_endpoints_tests.cpp:711 Value of: offeredResources.contains( allocatedResources(labeledResources2, frameworkInfo.roles(0))) Actual: false Expected: true Stack Trace: ../../src/tests/reservation_endpoints_tests.cpp:711 Value of: offeredResources.contains( allocatedResources(labeledResources2, frameworkInfo.roles(0))) Actual: false Expected: true FAILED: TaskGroupValidationTest.ShareCgroup Error Message: /tmp/SRC/src/tests/master_validation_tests.cpp:5336 Mock function called more times than expected - returning directly. Function call: statusUpdate(0x7ffd804641e8, @0x7f6558b0b1c0 136-byte object <B8-7C 00-66 65-7F 00-00 00-00 00-00 00-00 00-00 BE-A8 00-00 00-00 00-00 08-3A 52-63 65-7F 00-00 E0-B3 00-44 65-7F 00-00 F0-FA 00-44 65-7F 00-00 80-D5 00-44 65-7F 00-00 60-8A 02-44 65-7F 00-00 ... 00-00 00-00 00-00 00-00 60-91 02-44 65-7F 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 27-F7 5F-14 C1-88 D9-41 00-00 00-00 02-00 00-00 00-00 00-00 02-00 00-00>) Expected: to be called 4 times Actual: called 5 times - over-saturated and active Stack Trace: /tmp/SRC/src/tests/master_validation_tests.cpp:5336 Mock function called more times than expected - returning directly. Function call: statusUpdate(0x7ffd804641e8, @0x7f6558b0b1c0 136-byte object <B8-7C 00-66 65-7F 00-00 00-00 00-00 00-00 00-00 BE-A8 00-00 00-00 00-00 08-3A 52-63 65-7F 00-00 E0-B3 00-44 65-7F 00-00 F0-FA 00-44 65-7F 00-00 80-D5 00-44 65-7F 00-00 60-8A 02-44 65-7F 00-00 ... 00-00 00-00 00-00 00-00 60-91 02-44 65-7F 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 27-F7 5F-14 C1-88 D9-41 00-00 00-00 02-00 00-00 00-00 00-00 02-00 00-00>) Expected: to be called 4 times Actual: called 5 times - over-saturated and active FAILED: DockerFetcherPluginTest.INTERNET_CURL_FetchBlob Error Message: /tmp/SRC/src/tests/uri_fetcher_tests.cpp:355 (fetcher.get()->fetch(uri, dir)).failure(): Failed to perform 'curl' for 'https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/a3/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4/data?verify=1713573379-lHajU4QydZFIrfNwHiJvlwL0HKc%3D': curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. Stack Trace: /tmp/SRC/src/tests/uri_fetcher_tests.cpp:355 (fetcher.get()->fetch(uri, dir)).failure(): Failed to perform 'curl' for 'https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/a3/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4/data?verify=1713573379-lHajU4QydZFIrfNwHiJvlwL0HKc%3D': curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. FAILED: DockerFetcherPluginTest.INTERNET_CURL_FetchBlob Error Message: /tmp/SRC/src/tests/uri_fetcher_tests.cpp:355 (fetcher.get()->fetch(uri, dir)).failure(): Failed to perform 'curl' for 'https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/a3/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4/data?verify=1713573429-5dzaHOXC%2B9H5O8zny9L0PqybIns%3D': curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. Stack Trace: /tmp/SRC/src/tests/uri_fetcher_tests.cpp:355 (fetcher.get()->fetch(uri, dir)).failure(): Failed to perform 'curl' for 'https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/a3/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4/data?verify=1713573429-5dzaHOXC%2B9H5O8zny9L0PqybIns%3D': curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. FAILED: DockerFetcherPluginTest.INTERNET_CURL_FetchBlob Error Message: ../../../src/tests/uri_fetcher_tests.cpp:355 (fetcher.get()->fetch(uri, dir)).failure(): Failed to perform 'curl' for 'https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/a3/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4/data?verify=1713576143-H8iwJWKYg1L6KYZIHN9TUYhpha0%3D': curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. Stack Trace: ../../../src/tests/uri_fetcher_tests.cpp:355 (fetcher.get()->fetch(uri, dir)).failure(): Failed to perform 'curl' for 'https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/a3/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4/data?verify=1713576143-H8iwJWKYg1L6KYZIHN9TUYhpha0%3D': curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option.
