-
Notifications
You must be signed in to change notification settings - Fork 851
Closed
Description
Saw this failure in PR #7736. I think this is unrelated to the PR, so I am noting it here before I move on.
This is the output of the traffic_server process
[Apr 23 07:40:02.093] traffic_server DIAG: (TSContSchedule_test.init) initializing plugin for testing TSContScheduleOnThread
[Apr 23 07:40:02.144] [ET_TASK 1] DIAG: (TSContSchedule_test.schedule) [TSContSchedule_test] scheduling continuation
[Apr 23 07:40:02.145] [ET_NET 10] DIAG: (TSContSchedule_test.handler) TSContScheduleOnThread handler 1 thread [0x7f2637b4a010]
[Apr 23 07:40:02.145] [ET_NET 10] DIAG: (TSContSchedule_test.handler) [TSContSchedule_test] scheduling continuation
[Apr 23 07:40:02.145] [ET_NET 10] DIAG: (TSContSchedule_test.handler) TSContScheduleOnThread handler 2 thread [0x7f2637b4a010]
[Apr 23 07:40:02.145] [ET_NET 10] DIAG: (TSContSchedule_test.handler) TSContScheduleOnThread handler 2 thread [0x7f2637b4a010]
[Apr 23 07:40:02.145] [ET_NET 10] DIAG: (TSContSchedule_test.check) pass [should be the same thread]
Traffic Server 10.0.0 Apr 23 2021 07:24:41 docker-gd-2
traffic_server: using root directory '/var/tmp/ausb-7736.15400/schedule_on_thread/ts
The output is missing
(TSContSchedule_test.check) pass [should no be the same thread]
The test case command is just a print. The real test is launched from the plugin init. Perhaps the test is shutting down before the final bits of the test complete?