group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1681294@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package golang-1.6 - 1.6.2-0ubuntu5~16.04.2

---------------
golang-1.6 (1.6.2-0ubuntu5~16.04.2) xenial; urgency=medium

  * Fix build on ppc64el.

golang-1.6 (1.6.2-0ubuntu5~16.04.1) xenial; urgency=medium

  * Backport fix for ugly "pthread_create failed: Resource temporarily
    unavailable" message when calling syscall.Exec. (LP: #1681294)
  * Backport CL 29995 for tzdata 2016g changes.
  * Backport CL 37964 for tzdata 2017a changes.

 -- Michael Hudson-Doyle <michael.hudson@xxxxxxxxxx>  Wed, 12 Apr 2017
14:42:48 +1200

** Changed in: golang-1.6 (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1681294

Title:
  ugly "pthread_create failed: Resource temporarily unavailable" running
  snaps

Status in golang-1.6 package in Ubuntu:
  Invalid
Status in golang-1.7 package in Ubuntu:
  New
Status in golang-1.6 source package in Xenial:
  Fix Released
Status in golang-1.6 source package in Yakkety:
  Won't Fix

Bug description:
  [Impact]
  As reported here: https://lists.ubuntu.com/archives/snapcraft/2017-March/003497.html (and on internal lists), it is possible for a golang executable that calls syscall.Exec to print an ugly "pthread_create failed: Resource temporarily unavailable" message before it starts the new process. There is no functional effect, but snapd runs into this frequently so it interferes with a nice snappy experience.

  Luckily for us, the bug was fixed upstream in the 1.8 release
  (https://github.com/golang/go/issues/18146) so I can just backport the
  fix to Xenial and Yakkety.

  It also turns out to be necessary to include two more upstream patches
  that fix test suite failures with new tzdata packages.

  [Test case]
  Run this code:

  package main

  //
  import "C"

  import (
   "syscall"
  )

  func main() {
   syscall.Exec("/bin/true", []string{"/bin/true"}, nil)
  }

  a few thousand times and check for messages (it prints a message ~2%
  of the time or so without the fix).

  [Regression potential]
  The patch is simple, if a bit verbose (it has some per-architecture changes). It has not been the cause of any bug reports in 1.8 as far as I am aware. So I would characterise the regression potential as very low.

  The tzdata patches are similarly well exercised as they are backports,
  and are necessary or the build will fail!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1681294/+subscriptions