From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Go testing and resource exhaustion
Date: Sat, 25 May 2013 07:14:58 +0200 [thread overview]
Message-ID: <31f358500e3b7b565bf8cb9483f8710d@proxima.alt.za> (raw)
In-Reply-To: <CAJSxfm+yLz9tkmQCdVDNDiU01NdjyMucTtSoASps7pmh03kNiQ@mail.gmail.com>
> I'm seeing something that looks to me like a resource exhaustion of some
> sort. When running the standard test (i.e. go test std), some tests are
> broken (see below); but test of each "broken" package/cmd/etc, passes
> correctly.
I would agree with you, that is the impression I get as well, but the
little monitoring I've applied as well as the fact that I have three
very different hosts right here all exhibiting analogous but distinct
failures makes me think of time/performance related crashes.
On the other hand, cinap may be onto something: if we have a floating
point failure followed by a timer signal, all hell is perfectly
entitled to break loose. But floating point isn't always involved.
We'll get to the bottom of this, eventually, we just need as many
informative data points as possible.
++L
prev parent reply other threads:[~2013-05-25 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 21:57 Skip Tavakkolian
2013-05-25 5:14 ` lucio [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=31f358500e3b7b565bf8cb9483f8710d@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).