Branch: origin/master

Mesos » Mesos-Buildbot - Build # 267 - Still Failing:

Check console output at 
https://ci-builds.apache.org/job/Mesos/job/Mesos-Buildbot/267/ to view the 
results.

11 tests failed.
FAILED:  ReservationEndpointsTest.ReserveAndUnreserveNoAuthentication

Error Message:
/tmp/SRC/src/tests/reservation_endpoints_tests.cpp:1430
Value of: (response)->status
  Actual: "409 Conflict"
Expected: Accepted().status
Which is: "202 Accepted"
    Body: "ports:[31000-32000]; disk:3747251; cpus(reservations: 
[(DYNAMIC,role)]):1; mem(reservations: [(DYNAMIC,role)]):512 does not contain 
cpus:1; mem:512"

Stack Trace:
/tmp/SRC/src/tests/reservation_endpoints_tests.cpp:1430
Value of: (response)->status
  Actual: "409 Conflict"
Expected: Accepted().status
Which is: "202 Accepted"
    Body: "ports:[31000-32000]; disk:3747251; cpus(reservations: 
[(DYNAMIC,role)]):1; mem(reservations: [(DYNAMIC,role)]):512 does not contain 
cpus:1; mem:512"

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=1713313790-IEOQNapxO4a7yovEGp2lV6N4S3s%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=1713313790-IEOQNapxO4a7yovEGp2lV6N4S3s%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=1713315280-OmM8QA64j16Y0JFpMhKgrtN9%2BjQ%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=1713315280-OmM8QA64j16Y0JFpMhKgrtN9%2BjQ%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.DifferentPrincipalsSameRole

Error Message:
../../../src/tests/reservation_endpoints_tests.cpp:1514
Value of: resources.contains( allocatedResources(dynamicallyReserved2, 
frameworkInfo.roles(0)))
  Actual: false
Expected: true

Stack Trace:
../../../src/tests/reservation_endpoints_tests.cpp:1514
Value of: resources.contains( allocatedResources(dynamicallyReserved2, 
frameworkInfo.roles(0)))
  Actual: false
Expected: true

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=1713316047-9BRYCy%2Fkg2gpZ4HvZcz6fckAn3w%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=1713316047-9BRYCy%2Fkg2gpZ4HvZcz6fckAn3w%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:  OversubscriptionTest.FixedResourceEstimator

Error Message:
/tmp/SRC/src/tests/oversubscription_tests.cpp:718
Failed to wait 1mins for update1

Stack Trace:
/tmp/SRC/src/tests/oversubscription_tests.cpp:718
Failed to wait 1mins for update1

FAILED:  ReservationEndpointsTest.ReserveAndUnreserveNoAuthentication

Error Message:
/tmp/SRC/src/tests/reservation_endpoints_tests.cpp:1440
Value of: (response)->status
  Actual: "409 Conflict"
Expected: Accepted().status
Which is: "202 Accepted"
    Body: "ports:[31000-32000]; disk:3747251; cpus:1; mem:512 does not contain 
cpus(reservations: [(DYNAMIC,role,test-principal)]):1"

Stack Trace:
/tmp/SRC/src/tests/reservation_endpoints_tests.cpp:1440
Value of: (response)->status
  Actual: "409 Conflict"
Expected: Accepted().status
Which is: "202 Accepted"
    Body: "ports:[31000-32000]; disk:3747251; cpus:1; mem:512 does not contain 
cpus(reservations: [(DYNAMIC,role,test-principal)]):1"

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=1713314087-0ygOy0IjbSyXGGiid88bvqbPKwM%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=1713314087-0ygOy0IjbSyXGGiid88bvqbPKwM%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=1713315291-CVTXzcbD%2FlHtYjH3UGQRmf%2Bg7rk%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=1713315291-CVTXzcbD%2FlHtYjH3UGQRmf%2Bg7rk%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=1713312967-XdcpsUTXIrUnK%2BJEBqQhsTBWOLE%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=1713312967-XdcpsUTXIrUnK%2BJEBqQhsTBWOLE%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=1713313148-He421yjJ5KoQ6SFsdpuJrTbU%2F80%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=1713313148-He421yjJ5KoQ6SFsdpuJrTbU%2F80%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.

Reply via email to