We’ve found stress invaluable in helping to reproduce flaky tests
https://godoc.org/golang.org/x/tools/cmd/stress
On Sat, 17 Aug 2019 at 01:50, Maxim Fateev wrote:
> I wish Go had a deterministic execution mode with predefined randomization
> seed. The to reproduce such test you would only need
But as was pointed out, in this case it does not matter as the code is sharing
memory without proper synchronization so preemption doesn’t really matter.
> On Aug 16, 2019, at 11:29 PM, Ian Lance Taylor wrote:
>
>> On Fri, Aug 16, 2019 at 9:24 PM wrote:
>>
>> Could you let me know which comp
On Fri, Aug 16, 2019 at 8:09 PM wrote:
> The Go-Scheduler is unable to allow to switch to another goroutine in
> busy-waiting-loops -
> the only possibility to get around that problem is either to put
> "switch-steps" into the source
> - either "time.Sleep(1)" or "runtime.Gosched()".
> I think th
I feel the same way, Jean.
I quite don't get it a the first, and still some times i require to look
very well to distinguish the layout pattern for the string value beign
parsed.
El lunes, 14 de abril de 2014, 10:19:29 (UTC-3), Jean de Klerk escribió:
>
> In java, we do things like new SimpleDa
On Tue, Aug 13, 2019 at 11:13 AM Shulhan wrote:
>
> I am not sure where or how to report this problem, but all of the links
> from the following blog
>
> https://blog.golang.org/upcoming-google-io-go-events
>
> are 404. Some of examples,
>
> * http://code.google.com/events/io/2010/
> * ht
