Thanks for the instruction, I’ll take a look later. Regards Yunze Xu
> 2021年4月6日 上午1:38，Devin Bost <devin.b...@gmail.com> 写道： > > Check out the instructions by Lari Hotari here about how to setup your > personal Github CI: > https://markmail.org/message/xapp7aguh44osqhm > > I've been working through similar issues as I've been facing a > NullPointerException (in a PR of mine) that consistently occurs in Github > but never occurs locally. > > I tried using Act (https://github.com/nektos/act) to emulate the > environment but ran into different issues, probably permission related. > > -- > Devin G. Bost > > On Mon, Apr 5, 2021, 10:51 AM Yunze Xu <y...@streamnative.io.invalid> wrote: > >> This flaky test have existed for a long time, even before I contributed my >> first PR to Pulsar. I’ve been looking into the problem for several times >> but all blocked for that I cannot reproduce it in my local environment. >> >> From the code and logs, it looks like the cleanup phase encountered a >> segmentation fault, which may be caused by a possible null pointer >> accession in multi-thread test environment with >> https://github.com/google/gtest-parallel < >> https://github.com/google/gtest-parallel>. However, I still cannot >> reproduce it with the same command of CI. >> >> I just want to have a CI environment to test my ideas, but you know, the >> Pulsar’s workflows cost too much time, a tiny change may wait too long. Is >> there any way to run similar CI in my own repo and verify if the change >> could fix the flaky test? >> >> Regards >> Yunze Xu >> >>> 2021年4月2日 下午3:09，Enrico Olivelli <eolive...@gmail.com> 写道： >>> >>> Hello, >>> We have this BasicEndToEndTest.testLookupThrottling CPP test that is >> very flaky >>> >>> We already created two issues about it >>> https://github.com/apache/pulsar/issues/6301 >>> https://github.com/apache/pulsar/issues/6267 >>> >>> Is there any expert of the CPP client that can help in fixing this? >>> In my experience I see it failing very often on CI >>> >>> Regards >>> Enrico >> >>
