adoroszlai commented on PR #10523: URL: https://github.com/apache/ozone/pull/10523#issuecomment-4789947305
``` Key delete passthrough | FAIL | 4 != 0 ``` [failed here](https://github.com/apache/ozone/actions/runs/28097988687/job/83194765130?pr=10523#step:16:18) and in first attempt in fork. Unfortunately, check artifact is not available [due to](https://github.com/apache/ozone/actions/runs/28097988687/job/83194765130?pr=10523#step:17:24): ``` The path for one of the files in artifact is not valid: /ozone/ozone-prometheus-1_runtime exec failed: exec failed: unable to start container process: exec: "bash": executable file not found in $PATH .stack. Contains the following character: Double quote " ``` Originally reported it as follow-up (HDDS-15660), but looks like it would be better to fix it right in this PR. Please filter `prometheus` here: https://github.com/apache/ozone/blob/d1905e147a067c11fcc84097d62c793d280af442/hadoop-ozone/dist/src/main/compose/testlib.sh#L290-L299 like: ```diff diff --git hadoop-ozone/dist/src/main/compose/testlib.sh hadoop-ozone/dist/src/main/compose/testlib.sh index 903fdad7de..3c31de9b48 100755 --- hadoop-ozone/dist/src/main/compose/testlib.sh +++ hadoop-ozone/dist/src/main/compose/testlib.sh @@ -290,7 +290,7 @@ reorder_om_nodes() { ## @description Create stack dump of each java process in each container create_stack_dumps() { local c pid procname - for c in $(docker-compose ps | cut -f1 -d' ' | grep -e datanode -e om -e recon -e s3g -e scm); do + for c in $(docker-compose ps | cut -f1 -d' ' | grep -e datanode -e om -e recon -e s3g -e scm | grep -v -e prometheus); do while read -r pid procname; do echo "jstack $pid > ${RESULT_DIR}/${c}_${procname}.stack" docker exec "${c}" bash -c "jstack $pid" > "${RESULT_DIR}/${c}_${procname}.stack" ``` With that fix, we can get an artifact for the test run if it fails again, which may help determine if the failure is related to this change or not. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
