Actions
action #121366
closedunhandled error in t/04-scheduler that is not causing the test to fail
Description
Observation¶
https://app.circleci.com/pipelines/github/os-autoinst/openQA/10690/workflows/5ec5cebc-7983-48d2-a162-4f75a1ccef50/jobs/100198 from master branch shows the error:
[19:17:16] t/04-scheduler.t .......................................... 1/? [WARN] Failed to send data to websocket server, reason: fake error at t/04-scheduler.t line 35.
[WARN] Failed sending job(s) '1' to worker '1': unknown error
[19:17:16] t/04-scheduler.t .......................................... ok 8251 ms ( 0.02 usr 0.01 sys + 7.89 cusr 0.20 csys = 8.12 CPU)
IMHO this should fail the test but does not.
Updated by livdywan almost 2 years ago
- Status changed from New to In Progress
I don't think this should fail the test. The test explicitly creates this error in the socket mock. Although it would be good to consume the output here:
Updated by okurz almost 2 years ago
- Status changed from In Progress to Resolved
- Assignee set to livdywan
merged. https://app.circleci.com/pipelines/github/os-autoinst/openQA/10720/workflows/0added54-5801-4d83-936b-2c75c1e96a25/jobs/100456 shows no unhandled output. Thanks!
Actions