Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cudatoolkit: Several fixes #56018

Merged
merged 4 commits into from Mar 10, 2019
Merged

cudatoolkit: Several fixes #56018

merged 4 commits into from Mar 10, 2019

Conversation

knedlsepp
Copy link
Member

@knedlsepp knedlsepp commented Feb 18, 2019

Motivation for this change

The ncurses upgrade to libncurses.so.6 did silently break cuda-gdb quite some time ago. To reduce the chance of it breaking again we introduce simple smoke tests that do run all the programs shipped with
cudatoolkit. We add some fixes for the GUI applications, upgrade cudatoolkit-9.0 and make sure all older versions build.

#56826 Please backport to 19.03

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

The ncurses upgrade to libncurses.so.6 did silently break cuda-gdb quite
some time ago.
@knedlsepp knedlsepp changed the title cudatoolkit: Fixup cuda-gdb ncurses version cudatoolkit: Fixup cuda-gdb ncurses version + older versions Feb 18, 2019
@knedlsepp knedlsepp changed the title cudatoolkit: Fixup cuda-gdb ncurses version + older versions cudatoolkit: Several fixes Feb 18, 2019
@knedlsepp
Copy link
Member Author

Hm. It seems the issues with the GUI applications nvvp and nsight are related to #54278 (comment)

Versions prior to 9.0 did not build. Additionally we add some
smoke tests for the binaries in $out/bin.
This fixes the following error when starting nvvp or nsight:

```
(java:23876): Gtk-WARNING **: 19:12:17.777: Unable to locate theme engine in module_path: "adwaita",

A fatal error has been detected by the Java Runtime Environment:

 SIGSEGV (0xb) at pc=0x00007f957f7b67fe, pid=23876, tid=140281059333888

JRE version: Java(TM) SE Runtime Environment (8.0_77-b03) (build 1.8.0_77-b03)
Java VM: Java HotSpot(TM) 64-Bit Server VM (25.77-b03 mixed mode linux-amd64 compressed oops)
Problematic frame:
C  [libpixbufloader-bmp.so+0x27fe]  gdk_pixbuf__bmp_image_load_increment+0xeee
```

Since GDK_PIXBUF_MODULE_FILE should match the version we actually link
to, we override the environment variable using the one provided by the
gdk_pixbuf setup-hook.
@knedlsepp
Copy link
Member Author

@Mic92 Would you mind having a look at these fixes?

@FRidh FRidh added this to the 19.03 milestone Mar 5, 2019
@bendlas
Copy link
Contributor

bendlas commented Mar 10, 2019

confirmed failure, fix and lgtm

@bendlas bendlas merged commit b854767 into NixOS:master Mar 10, 2019
bendlas added a commit that referenced this pull request Mar 10, 2019
cudatoolkit: Several fixes
(cherry picked from commit b854767)
@knedlsepp
Copy link
Member Author

Thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants