lostluck commented on issue #28951: URL: https://github.com/apache/beam/issues/28951#issuecomment-1760360659
It's definitely a prism thing, and not this specific test. Recently there were other failures (which have been fixed) due to an uncompiled change failure change (unused import). I see a few test timeouts. I see a few "runner ran out of memory" (https://github.com/apache/beam/pull/28954 should help there) by properly caching go deps. I see a couple where govulncheck is taking ages (this has now been removed, which will help). One "send on a closed channel" which is definitely a race condition (and statistically likely to be the root cause of the timeouts). https://github.com/apache/beam/actions/runs/6432180597/job/17466495105 https://github.com/apache/beam/actions/runs/6424305310/job/17444659174 -- 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]
