Connector Performance Harness Cron #2
connector-performance-cron.yml
on: schedule
mongodb-1m-run-incremental
/
Custom UUID of workflow run
0s
mysql-1m-run-incremental
/
Custom UUID of workflow run
0s
mysql-1m-run
/
Custom UUID of workflow run
0s
postgres-1m-run-incremental
/
Custom UUID of workflow run
0s
postgres-1m-run
/
Custom UUID of workflow run
0s
mongodb-1m-run-incremental
/
Start Build EC2 Runner
9s
mysql-1m-run-incremental
/
Start Build EC2 Runner
11s
postgres-1m-run-incremental
/
Start Build EC2 Runner
8s
mongodb-1m-run-incremental
/
Stop Build EC2 Runner
5s
mysql-1m-run-incremental
/
Stop Build EC2 Runner
2s
mysql-1m-run
/
Stop Build EC2 Runner
5s
postgres-1m-run-incremental
/
Stop Build EC2 Runner
5s
postgres-1m-run
/
Stop Build EC2 Runner
5s
Annotations
10 errors and 5 warnings
postgres-1m-run-incremental / Start Build EC2 Runner
Process completed with exit code 1.
|
mysql-1m-run-incremental / Start Build EC2 Runner
Process completed with exit code 1.
|
mysql-1m-run / Start Build EC2 Runner
Process completed with exit code 1.
|
mongodb-1m-run-incremental / Start Build EC2 Runner
Process completed with exit code 1.
|
postgres-1m-run / Start Build EC2 Runner
Process completed with exit code 1.
|
mysql-1m-run-incremental / Stop Build EC2 Runner
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
|
postgres-1m-run-incremental / Stop Build EC2 Runner
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
|
postgres-1m-run / Stop Build EC2 Runner
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
|
mongodb-1m-run-incremental / Stop Build EC2 Runner
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
|
mysql-1m-run / Stop Build EC2 Runner
Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers
|
mysql-1m-run-incremental / Stop Build EC2 Runner
The following actions uses node12 which is deprecated and will be forced to run on node16: aws-actions/configure-aws-credentials@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
postgres-1m-run-incremental / Stop Build EC2 Runner
The following actions uses node12 which is deprecated and will be forced to run on node16: aws-actions/configure-aws-credentials@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
postgres-1m-run / Stop Build EC2 Runner
The following actions uses node12 which is deprecated and will be forced to run on node16: aws-actions/configure-aws-credentials@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
mongodb-1m-run-incremental / Stop Build EC2 Runner
The following actions uses node12 which is deprecated and will be forced to run on node16: aws-actions/configure-aws-credentials@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
mysql-1m-run / Stop Build EC2 Runner
The following actions uses node12 which is deprecated and will be forced to run on node16: aws-actions/configure-aws-credentials@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|