Thanks for the efforts! I followed up on INFRA-17335 <https://issues.apache.org/jira/browse/INFRA-17335> and slack thread. And also created https://issues.apache.org/jira/browse/INFRA-18070 to track this issue separately. Hope this can help!
Mark On Wed, Mar 20, 2019 at 7:43 PM Valentyn Tymofieiev <[email protected]> wrote: > I asked them yesterday on Slack, and commented on existing issue > https://issues.apache.org/jira/browse/INFRA-17335, however didn't receive > a response. We can try opening another infra ticket. Mark, perhaps you can > quote/+1 my message from yesterday in thier slack channel :) ? > > On Wed, Mar 20, 2019 at 6:23 PM Yifan Zou <[email protected]> wrote: > >> You could try to ping them in the slack channel >> https://the-asf.slack.com/messages/ if it is really urgent. >> >> On Wed, Mar 20, 2019 at 5:29 PM Mark Liu <[email protected]> wrote: >> >>> Hi, >>> >>> I saw occasional py36 tox test failure in beam_PreCommit_Python >>> and beam_Release_NightlySnapshot in cron job >>> <https://builds.apache.org/job/beam_PreCommit_Python_Cron/1087/> as >>> well as PR triggered job >>> <https://builds.apache.org/job/beam_Release_NightlySnapshot/374/>. The >>> error is simple: >>> >>> ERROR: InterpreterNotFound: python3.6 >>> >>> Turns out those failures only happened in Beam2 and Beam12. From console >>> log of inventory jobs (beam2 >>> <https://builds.apache.org/job/beam_Inventory_beam2/358/console> and >>> beam12 <https://builds.apache.org/job/beam_Inventory_beam12/324/console>), >>> I found python3.6 and python3.7 interpreters are missing. This makes >>> beam_PreCommit_Python_Cron >>> <https://builds.apache.org/job/beam_PreCommit_Python_Cron/> flaky >>> recently and may fail any python build that runs on those two nodes. >>> >>> Infra team helped install Python3 on our Jenkins before, but they were >>> slow for response on JIRA. What's the best way to have Infra team get >>> involved to this problem? >>> >>> Thanks, >>> Mark >>> >>
