Merge branch 'test/funcionaltests' of https://github.com/elastic/apm-… #1
v1vfunctional-tests.yml
on: push
Matrix: run
All Smoke Tests
3s
Annotations
2 errors and 2 warnings
|
run (pro)
google-github-actions/auth failed with: failed to generate Google Cloud federated token for //iam.googleapis.com/projects/8560181848/locations/global/workloadIdentityPools/github/providers/repo-7a55670bf6cfa458b579333c456: {"error":"invalid_target","error_description":"The target service indicated by the \"audience\" parameters is invalid. This might either be because the pool or provider is disabled or deleted or because it doesn't exist."}
|
|
run (qa)
google-github-actions/auth failed with: failed to generate Google Cloud federated token for //iam.googleapis.com/projects/8560181848/locations/global/workloadIdentityPools/github/providers/repo-7a55670bf6cfa458b579333c456: {"error":"invalid_target","error_description":"The target service indicated by the \"audience\" parameters is invalid. This might either be because the pool or provider is disabled or deleted or because it doesn't exist."}
|
|
All Smoke Tests
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
|
|
All Smoke Tests
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).
|