Krystian Chmura
Krystian Chmura
@mdelapenya I will try in the weekend. Perhaps problem is somewhere in the `StartLogProducer`. The logic is so weird, that I need to some time to analyse it: for example...
Calling make with an option `--load-average` can be a good workaround e.g: ```bash NUMBER_OF_CPUS= "$(grep -c processor /proc/cpuinfo)" make -j "$NUMBER_OF_CPUS" -l "$NUMBER_OF_CPUS" ```
@fuhailin I don't know, `/proc/cpuinfo` was just a quick thought. You can specifiy flags in bazel command to limit cpu like `--local_cpu_resources` or `--jobs` to reduce number of concurrent tasks....
> Is there a way to achieve that using the existing implementation or would require development effort? I don't think so. Current metrics keep only status for the last run....
@codeit14 #206 is merged and released. Could you verify, if it works for you?
@alexisvisco do you work on this PR anymore?
@rsc @mdempsky can you merge it? I have encountered this bug today and that commit fix it
@vearutop if you need a great replacement then try https://github.com/uber-go/gopatch
> It is expected for Golang APIs to be context-aware by default Context-aware means that you receive `ctx` in a function/method params and you support cancellation based on that `ctx`...
@ThisIsAreku for me we can merge either one PR