shuke987 opened a new pull request, #65234:
URL: https://github.com/apache/doris/pull/65234

   ## Proposed changes
   
   `test_audit_log_internal_query_failure` validates that a failed internal 
stats
   query is audited as `ERR`. The case currently finds the audit row by 
requiring
   `queried_tables_and_views` to contain the exact user table name.
   
   That auxiliary field is brittle for the failed internal-query path. In the
   latest branch-4.1 failure, the injected tablet-scoped `IO_ERROR` happened, 
but
   the audit lookup stayed empty because of the exact `queried_tables_and_views`
   filter.
   
   This PR keeps the product assertion but matches the audit row by the evidence
   that uniquely belongs to this run:
   
   - `is_internal = 1`
   - `state = 'ERR'`
   - `error_message` contains `IO_ERROR`
   - `error_message` contains the injected `tabletId`
   - `time >= startTime`
   
   It also logs the recent internal audit rows if the lookup still fails, so the
   next failure is easier to diagnose.
   
   ## Evidence
   
   - Branch-4.1 TeamCity history: 20 failures / 612 occurrences for
     
`fault_injection_p0.test_audit_log_internal_query_failure.test_audit_log_internal_query_failure`.
   - Latest checked failure: build 985138 / PR 65191, assertion:
     `expected an audit_log entry with state=ERR for the failed gather query`.
   - Build 985138 reached the intended injected `IO_ERROR` during
     `analyze table test_audit_log_internal_query_failure_t1 with sync`.
   - Build 985138 used a branch-4.1 base containing #65132 before merging PR 
65191,
     so this is not only the older audit-loader batch assembly race.
   
   ## Testing
   
   - `git diff --check`
   - `groovy -e 'new GroovyShell().parse(new File(args[0])); println "OK"' 
regression-test/suites/fault_injection_p0/test_audit_log_internal_query_failure.groovy`
   
   


-- 
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]

Reply via email to