lhotari commented on issue #13663: URL: https://github.com/apache/pulsar/issues/13663#issuecomment-1031180848
> @lhotari Hi,I have tested the master branch for tens of thousands of times, and the not reproduce. I guess the above error is because PR is not rebase master, and this SHA maybe not included. The PR run included the previous fix. I check this failure: [example failure 2022-01-31T08:43:50.8742741Z](https://github.com/apache/pulsar/runs/5002911603?check_suite_focus=true?check_suite_focus=true#step:8:6996) From the logs, you can see the revision for the build, it's [`a4cca4544615e1aeb62884066f1c6e3c79f6973d`](https://github.com/apache/pulsar/runs/5002911603?check_suite_focus=true?check_suite_focus=true#step:2:479) You can check that it's included: ``` git fetch origin a4cca4544615e1aeb62884066f1c6e3c79f6973d git checkout a4cca4544615e1aeb62884066f1c6e3c79f6973d git log --grep="LockManagerTest.updateValue" ``` @shibd A lot of the problem in CI don't reproduce locally unless you simulate the CI environment by restricting the CPU & Memory resources. The GitHub Actions CI has 2 virtual CPUs and 7GB of RAM. I have been using a solution where I run tests in docker with `--cpus=0.8`. That usually reproduces issues which only happen with limited CPU resources. I have some shell functions in https://github.com/lhotari/pulsar-contributor-toolbox . The solution is for Linux docker environments. Using the solution in pulsar-contributor-toolbox (this works only on Linux): ``` ptbx_build_coremodules ptbx_until_test_fails_in_docker_with_logs --cpus=0.8 -pl pulsar-metadata -Dtest=LockManagerTest#updateValue ``` I tried a couple of rounds, but wasn't able to reproduce. It's possible that it's just very hard to reproduce. -- 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]
