Comments (8)
I see the same issue at Arch Linux:
33/185 Test #33: credentials_provider_ecs_basic_success ........................................ Passed 0.01 sec
Start 34: credentials_provider_ecs_no_auth_token_success
34/185 Test #34: credentials_provider_ecs_no_auth_token_success ................................ Passed 0.01 sec
Start 35: credentials_provider_ecs_success_multi_part_doc
35/185 Test #35: credentials_provider_ecs_success_multi_part_doc ............................... Passed 0.00 sec
Start 36: credentials_provider_ecs_real_new_destroy
36/185 Test #36: credentials_provider_ecs_real_new_destroy ..................................... Passed 1.20 sec
Start 37: credentials_provider_x509_new_destroy
37/185 Test #37: credentials_provider_x509_new_destroy ......................................... Passed 0.06 sec
Start 38: credentials_provider_x509_connect_failure
38/185 Test #38: credentials_provider_x509_connect_failure ..................................... Passed 0.02 sec
Start 39: credentials_provider_x509_request_failure
39/185 Test #39: credentials_provider_x509_request_failure ..................................... Passed 0.02 sec
Start 40: credentials_provider_x509_bad_document_failure
40/185 Test #40: credentials_provider_x509_bad_document_failure ................................ Passed 0.02 sec
Start 41: credentials_provider_x509_basic_success
41/185 Test #41: credentials_provider_x509_basic_success ....................................... Passed 0.02 sec
Start 42: credentials_provider_x509_success_multi_part_doc
42/185 Test #42: credentials_provider_x509_success_multi_part_doc .............................. Passed 0.02 sec
Start 43: credentials_provider_x509_real_new_destroy
43/185 Test #43: credentials_provider_x509_real_new_destroy ....................................***Failed 0.14 sec
Start 44: credentials_provider_sts_web_identity_new_destroy_from_env
from aws-c-auth.
That doesn't look like the same thing. What happens when you run the failing test individually and get log output?
from aws-c-auth.
That doesn't look like the same thing. What happens when you run the failing test individually and get log output?
interesting that after I updated all aws-c-* dependencies to the latest version this test problem has gone for me.
from aws-c-auth.
As of the current moment, the aws-c-* libraries are not guaranteed ABI-compatible unless taken as a snapshot. It feels like we're getting packaging/distribution issues here and there and we need to lock that down, but I don't have any kind of ETA.
from aws-c-auth.
@bretambrose I think the main issue that needs to be sorted out with the aws-c-* libraries are the non-standard cmake paths.
The proper path for cmake files is /usr/lib{,64}/cmake/${AWS_MODULE_PATH}
, yet all aws-c-* packages install into /usr/lib{,64}/${AWS_MODULE_PATH}/cmake
.
See awslabs/aws-c-event-stream#15 and awslabs/aws-c-common#844.
from aws-c-auth.
Understandable and I've skimmed all of those path/packaging issues but I don't feel personally comfortable tweaking those due to a lack of expertise and the $*%#-storm that will happen if the path changes break anything in how the libraries are built/consumed internally within Amazon's build systems and platforms. @JonathanHenson might be able to provide more knowledgable support there.
from aws-c-auth.
As long as the changes are all made at once our build system won't care. The problem, of course is synchronizing that and making sure all consumers rebuild everything when they build their dependency closure. Maybe we could bootstrap the find_package scripts to check both paths until the next minor version revision?
from aws-c-auth.
Please make sure that you are using the latest version of all of repo's. If you still run into any testsuite problems please open a new issue
from aws-c-auth.
Related Issues (13)
- ECS Credentials Provider results in status code 400 (Bad Request) HOT 2
- Allow ECS credential provider ports to be configured to enable binding and integration testing HOT 1
- FreeBSD systems require -lexecinfo flag HOT 1
- Potentially missing test files for sigV4 HOT 1
- Clarification on SigV4 test encoding HOT 1
- default chain provider: add support for SSO generated credentials HOT 1
- [STS web identity] TLS negotiation timeout too small HOT 2
- IMDSv2 credentials provider hangs forever from Docker container HOT 1
- `aws_credentials_provider_new_chain_default` hangs without ever calling credentialsCallBack HOT 4
- BUILD_TESTING=ON causes link error since version 0.6.26 HOT 2
- Default provider chain does not support SSO profile-defined credentials HOT 1
- Request for documentation of every parameter HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aws-c-auth.