FAQ
I cleaned up the failing test a little, and both darwin-386 builders
and the linux-386 builder fail one of the go.crypto tests with a
message like:
2013/04/17 17:54:37 user.Current: user: Current not implemented on
darwin/386; falling back on $USER
(and obviously s/darwin/linux/ for the linux-386 builder).

From what I can tell, that implies that cgo is disabled on those
builders, because that error comes from the stubs in os/user.

Who owns those builders? Why is cgo disabled?

--

---
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

  • Brad Fitzpatrick at Apr 17, 2013 at 2:32 pm
    Hover over the goarch in the build.golang.org headings and then see:

    https://code.google.com/p/go-wiki/wiki/DashboardBuilders

    ... to find the owner.

    I believe cgo was disabled on some builders intentionally to flesh out
    coverage.


    On Wed, Apr 17, 2013 at 2:06 AM, David Symonds wrote:

    I cleaned up the failing test a little, and both darwin-386 builders
    and the linux-386 builder fail one of the go.crypto tests with a
    message like:
    2013/04/17 17:54:37 user.Current: user: Current not implemented on
    darwin/386; falling back on $USER
    (and obviously s/darwin/linux/ for the linux-386 builder).

    From what I can tell, that implies that cgo is disabled on those
    builders, because that error comes from the stubs in os/user.

    Who owns those builders? Why is cgo disabled?

    --

    ---
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Dave Cheney at Apr 18, 2013 at 12:18 am
    Hmm, that is odd, the two darwin/386 builders are both reporting they
    cannot get $USER. The leftmost is adg's 10.6 machine, the next is my
    10.7 machine. There is nothing special about those builders, and as my
    darwin builder is building darwin/386, darwin/amd64 and
    darwin/amd64-race an unintentional disabling of cgo should affect all
    three right ?
    On Thu, Apr 18, 2013 at 12:32 AM, Brad Fitzpatrick wrote:
    Hover over the goarch in the build.golang.org headings and then see:

    https://code.google.com/p/go-wiki/wiki/DashboardBuilders

    ... to find the owner.

    I believe cgo was disabled on some builders intentionally to flesh out
    coverage.


    On Wed, Apr 17, 2013 at 2:06 AM, David Symonds wrote:

    I cleaned up the failing test a little, and both darwin-386 builders
    and the linux-386 builder fail one of the go.crypto tests with a
    message like:
    2013/04/17 17:54:37 user.Current: user: Current not implemented on
    darwin/386; falling back on $USER
    (and obviously s/darwin/linux/ for the linux-386 builder).

    From what I can tell, that implies that cgo is disabled on those
    builders, because that error comes from the stubs in os/user.

    Who owns those builders? Why is cgo disabled?

    --

    ---
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
    --

    ---
    You received this message because you are subscribed to the Google Groups
    "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • David Symonds at Apr 18, 2013 at 12:21 am
    Just an idea: https://codereview.appspot.com/8821046

    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • David Symonds at Apr 18, 2013 at 1:06 am
    Can the owners of builders currently breaking on go.crypto (I believe
    Cheney, Fitzpatrick and Gerrand) please sync, build and restart your
    builders? I've submitted https://codereview.appspot.com/8821046, which
    should hopefully get everything fixed.

    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Dave Cheney at Apr 18, 2013 at 1:14 am
    Thanks, done.
    On Thu, Apr 18, 2013 at 11:06 AM, David Symonds wrote:
    Can the owners of builders currently breaking on go.crypto (I believe
    Cheney, Fitzpatrick and Gerrand) please sync, build and restart your
    builders? I've submitted https://codereview.appspot.com/8821046, which
    should hopefully get everything fixed.
    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Dave Cheney at Apr 18, 2013 at 1:18 am
    Oh -- i think I know what is causing the problem.
    https://codereview.appspot.com/8134043 disabled cgo when cross
    compiling -- our darwin/* builders must be the only ones cross
    compiling.

    On Thu, Apr 18, 2013 at 11:14 AM, Dave Cheney wrote:
    Thanks, done.
    On Thu, Apr 18, 2013 at 11:06 AM, David Symonds wrote:
    Can the owners of builders currently breaking on go.crypto (I believe
    Cheney, Fitzpatrick and Gerrand) please sync, build and restart your
    builders? I've submitted https://codereview.appspot.com/8821046, which
    should hopefully get everything fixed.
    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Dave Cheney at Apr 18, 2013 at 2:19 am
    This was indeed the case. I watched the build on my darwin-386-cheney
    builder and saw it was skipping the cgo steps.

    https://codereview.appspot.com/8842044 should fix the problem. I've
    patched this into my builder and will hg mail it once I've confirmed
    it has worked with the next build commit.

    Cheers

    Dave
    On Thu, Apr 18, 2013 at 11:18 AM, Dave Cheney wrote:
    Oh -- i think I know what is causing the problem.
    https://codereview.appspot.com/8134043 disabled cgo when cross
    compiling -- our darwin/* builders must be the only ones cross
    compiling.

    On Thu, Apr 18, 2013 at 11:14 AM, Dave Cheney wrote:
    Thanks, done.
    On Thu, Apr 18, 2013 at 11:06 AM, David Symonds wrote:
    Can the owners of builders currently breaking on go.crypto (I believe
    Cheney, Fitzpatrick and Gerrand) please sync, build and restart your
    builders? I've submitted https://codereview.appspot.com/8821046, which
    should hopefully get everything fixed.
    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Dave Cheney at Apr 18, 2013 at 6:44 am
    With apologies, could the owners of

    darwin-386
    linux-amd64
    linux-386

    please update their builders to revision 654eb0e0adf4.
    On Thu, Apr 18, 2013 at 12:19 PM, Dave Cheney wrote:
    This was indeed the case. I watched the build on my darwin-386-cheney
    builder and saw it was skipping the cgo steps.

    https://codereview.appspot.com/8842044 should fix the problem. I've
    patched this into my builder and will hg mail it once I've confirmed
    it has worked with the next build commit.

    Cheers

    Dave
    On Thu, Apr 18, 2013 at 11:18 AM, Dave Cheney wrote:
    Oh -- i think I know what is causing the problem.
    https://codereview.appspot.com/8134043 disabled cgo when cross
    compiling -- our darwin/* builders must be the only ones cross
    compiling.

    On Thu, Apr 18, 2013 at 11:14 AM, Dave Cheney wrote:
    Thanks, done.
    On Thu, Apr 18, 2013 at 11:06 AM, David Symonds wrote:
    Can the owners of builders currently breaking on go.crypto (I believe
    Cheney, Fitzpatrick and Gerrand) please sync, build and restart your
    builders? I've submitted https://codereview.appspot.com/8821046, which
    should hopefully get everything fixed.
    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Brad Fitzpatrick at Apr 18, 2013 at 3:08 pm
    Linux is done.


    On Wed, Apr 17, 2013 at 11:44 PM, Dave Cheney wrote:

    With apologies, could the owners of

    darwin-386
    linux-amd64
    linux-386

    please update their builders to revision 654eb0e0adf4.
    On Thu, Apr 18, 2013 at 12:19 PM, Dave Cheney wrote:
    This was indeed the case. I watched the build on my darwin-386-cheney
    builder and saw it was skipping the cgo steps.

    https://codereview.appspot.com/8842044 should fix the problem. I've
    patched this into my builder and will hg mail it once I've confirmed
    it has worked with the next build commit.

    Cheers

    Dave
    On Thu, Apr 18, 2013 at 11:18 AM, Dave Cheney wrote:
    Oh -- i think I know what is causing the problem.
    https://codereview.appspot.com/8134043 disabled cgo when cross
    compiling -- our darwin/* builders must be the only ones cross
    compiling.

    On Thu, Apr 18, 2013 at 11:14 AM, Dave Cheney wrote:
    Thanks, done.
    On Thu, Apr 18, 2013 at 11:06 AM, David Symonds wrote:
    Can the owners of builders currently breaking on go.crypto (I believe
    Cheney, Fitzpatrick and Gerrand) please sync, build and restart your
    builders? I've submitted https://codereview.appspot.com/8821046,
    which
    should hopefully get everything fixed.
    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Andrew Gerrand at Apr 19, 2013 at 3:41 pm
    darwin-amd64 and darwin-386 are done.

    On 18 April 2013 16:44, Dave Cheney wrote:

    With apologies, could the owners of

    darwin-386
    linux-amd64
    linux-386

    please update their builders to revision 654eb0e0adf4.
    On Thu, Apr 18, 2013 at 12:19 PM, Dave Cheney wrote:
    This was indeed the case. I watched the build on my darwin-386-cheney
    builder and saw it was skipping the cgo steps.

    https://codereview.appspot.com/8842044 should fix the problem. I've
    patched this into my builder and will hg mail it once I've confirmed
    it has worked with the next build commit.

    Cheers

    Dave
    On Thu, Apr 18, 2013 at 11:18 AM, Dave Cheney wrote:
    Oh -- i think I know what is causing the problem.
    https://codereview.appspot.com/8134043 disabled cgo when cross
    compiling -- our darwin/* builders must be the only ones cross
    compiling.

    On Thu, Apr 18, 2013 at 11:14 AM, Dave Cheney wrote:
    Thanks, done.
    On Thu, Apr 18, 2013 at 11:06 AM, David Symonds wrote:
    Can the owners of builders currently breaking on go.crypto (I believe
    Cheney, Fitzpatrick and Gerrand) please sync, build and restart your
    builders? I've submitted https://codereview.appspot.com/8821046,
    which
    should hopefully get everything fixed.
    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Minux at Apr 18, 2013 at 3:13 pm

    On Thu, Apr 18, 2013 at 9:18 AM, Dave Cheney wrote:

    Oh -- i think I know what is causing the problem.
    https://codereview.appspot.com/8134043 disabled cgo when cross
    compiling -- our darwin/* builders must be the only ones cross
    compiling.
    we probably should document this change to cmd/go in doc/go1.1.html

    if it is causing problems for us, no doubt it will cause problems for the
    users.

    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Dave Cheney at Apr 18, 2013 at 3:15 pm
    I'm fairly sure it is documented. Please let me know if the description needs to be expanded.


    On 19/04/2013, at 1:12 AM, minux wrote:

    On Thu, Apr 18, 2013 at 9:18 AM, Dave Cheney wrote:
    Oh -- i think I know what is causing the problem.
    https://codereview.appspot.com/8134043 disabled cgo when cross
    compiling -- our darwin/* builders must be the only ones cross
    compiling.
    we probably should document this change to cmd/go in doc/go1.1.html

    if it is causing problems for us, no doubt it will cause problems for the users.
    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Minux at Apr 18, 2013 at 4:00 pm

    On Thu, Apr 18, 2013 at 11:14 PM, Dave Cheney wrote:

    I'm fairly sure it is documented. Please let me know if the description
    needs to be expanded.
    oops, sorry, i didn't find it on my last read.

    --

    ---
    You received this message because you are subscribed to the Google Groups "golang-dev" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-dev @
categoriesgo
postedApr 17, '13 at 9:06a
activeApr 19, '13 at 3:41p
posts14
users5
websitegolang.org

People

Translate

site design / logo © 2022 Grokbase