bneradt commented on PR #9664: URL: https://github.com/apache/trafficserver/pull/9664#issuecomment-1530578191
It seems like somehow your PR is impacting the behavior of the immediate shutdown oriented tests. The ones that misconfigure ATS then expect certain logs and response codes: https://ci.trafficserver.apache.org/job/Github_Builds/job/autest/6935/console ``` Test : Checking that ReturnCode == 33 - Failed Reason: Returned Value -2 != 33 Time-Out : Process finishes within expected time - Passed Reason: Returned value: 1.0000324249267578 < 600.0 file /tmp/sandbox/emergency/ts/log/diags.log : should contain "testing emergency shutdown" - Failed Reason: Cannot read /tmp/sandbox/emergency/ts/log/diags.log: [Errno 2] No such file or directory: '/tmp/sandbox/emergency/ts/log/diags.log' file /tmp/sandbox/emergency/ts/log/traffic.out : should NOT contain "failed to shutdown" - Failed Reason: Cannot read /tmp/sandbox/emergency/ts/log/traffic.out: [Errno 2] No such file or directory: '/tmp/sandbox/emergency/ts/log/traffic.out' ``` Note the difference in return code (-2 instead of 33) and the diags.log and traffic.out files are not there. These tests are generally pretty reliable in master - your other recent PRs haven't failed these tests. Unfortunately, the archived sandbox doesn't have much information, since none of the logs were emitted: https://ci.trafficserver.apache.org/job/Github_Builds/job/autest/6935/artifact/output/9664/sandbox/emergency/ -- 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]
