Added GuanceCloud partner #419
Conversation
| name: datakit-test-cronjob | ||
| namespace: datakit | ||
| spec: | ||
| schedule: "* */12 * * *" |
There was a problem hiding this comment.
@baihongru, can you change this to "0 */12 * * *"? That way it will only run twice a day
There was a problem hiding this comment.
Already submitted, the account and other test information have been sent to [email protected]
|
/test-e2e |
|
|
||
| http_code=$(echo "$response" | awk '/^ HTTP/{print $2}' | head -n 1) | ||
|
|
||
| if [ $? -ne 0 ] && [ -n "$http_code" ] && [ "$http_code" -ge 200 ] && [ "$http_code" -lt 300 ]; then |
There was a problem hiding this comment.
This lines first condition is inverted. It should pass if the wget command returns 0. Should be fixed if replaced with the following:
if [ $? -eq 0 ] && [ -n "$http_code" ] && [ "$http_code" -ge 200 ] && [ "$http_code" -lt 300 ]; then
There was a problem hiding this comment.
Thanks, the modifications have been submitted.
|
@baihongru it looks like the app is deploying successfully, and logs are populating in the dashboard, but I do not see the log from the test in the dashboard even though it prints write log success. Any ideas as to why? |
|
@zjaco13 
|
|
@zjaco13 Due to the excessive volume of test cluster logs, I have configured the Pipeline to discard the logs of non-test tasks. Please visit the following link to view the configuration: |
|
@baihongru, I'm not seeing any logs for the 22 hours, and also logs aren't populating when I run the test manually. Could this be due to the pipeline configuration? |
|
@zjaco13 Sorry, it was indeed a problem with the Pipeline configuration. It has been fixed. The log sending method used in the test task has specific settings, and my previous tests only covered the common log collection method. Now you can re-test. 
|
|
@zjaco13 Due to the excessive data generated during the test, my test account has run out of funds. It is possible that data writing will be prohibited after one day. Currently, I am following up on the process to solve this problem. |
@baihongru Sounds good, please let me know when I can resume testing. |
|
@zjaco13 The issue regarding the testing account fees has been resolved and it's now ready for testing. |
2 participants
I'm very sorry that this task has been interrupted for a long time.
For the background information, please refer to the previous PR #377.
The previous issue has now been resolved by modifying the repository address in the PR. The test-related accounts will be sent to you via email.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.