Bug 928938 – dev-dotnet/dotnet-sdk-8.0.102 - build failed

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Toralf Förster 2024-04-08 17:14:54 UTC]

/var/tmp/portage/dev-dotnet/dotnet-sdk-8.0.102/work/dotnet-sdk-8.0.2/build.proj(123,5): error MSB4018:    at Microsoft.DotNet.Build.Tasks.CreateSdkSymbolsLayout.IndexAllSymbols()
/var/tmp/portage/dev-dotnet/dotnet-sdk-8.0.102/work/dotnet-sdk-8.0.2/build.proj(123,5): error MSB4018:    at Microsoft.DotNet.Build.Tasks.CreateSdkSymbolsLayout.Execute()
/var/tmp/portage/dev-dotnet/dotnet-sdk-8.0.102/work/dotnet-sdk-8.0.2/build.proj(123,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
/var/tmp/portage/dev-dotnet/dotnet-sdk-8.0.102/work/dotnet-sdk-8.0.2/build.proj(123,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask)
 [ !! ]
 * ERROR: dev-dotnet/dotnet-sdk-8.0.102::gentoo failed (compile phase):
 *   build failed
 * 
 * Call stack:

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 23.0_musl-20240403-202925

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-musl-13 *
clang/llvm (if any):
clang version 18.1.3
Target: x86_64-pc-linux-musl
Thread model: posix
InstalledDir: /usr/lib/llvm/18/bin
Configuration file: /etc/clang/x86_64-pc-linux-musl-clang.cfg
/usr/lib/llvm/18
18.1.3
Python 3.11.9
Available Ruby profiles:
  [1]   ruby31 (with Rubygems)
  [2]   ruby32 (with Rubygems)
  [3]   ruby33 (with Rubygems) *
Available Rust versions:
  [1]   rust-bin-1.77.1
  [2]   rust-1.77.1 *
The following VMs are available for generation-2:
1)	Eclipse Temurin JDK 17.0.10_p7 [openjdk-bin-17]
*)	Eclipse Temurin JDK 21.0.2_p13 [openjdk-bin-21]
Available Java Virtual Machines:
  [1]   openjdk-bin-17 
  [2]   openjdk-bin-21  system-vm

php cli (if any):
  [1]   php8.1
  [2]   php8.3 *
go version go1.22.1 linux/amd64

  HEAD of ::gentoo
commit b203e8a0a25ff00b738581e496c5fa86eaafff33
Author: Repository mirror & CI <[e-mail]>
Date:   Sun Apr 7 19:34:12 2024 +0000

    2024-04-07 19:34:11 UTC

emerge -qpvO dev-dotnet/dotnet-sdk
[ebuild  N    ] dev-dotnet/dotnet-sdk-8.0.102

[Comment 1 Toralf Förster 2024-04-08 17:14:54 UTC]

Created attachment 889824 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2024-04-08 17:14:56 UTC]

Created attachment 889825 [details]
dev-dotnet:dotnet-sdk-8.0.102:20240407-203911.log.xz

[Comment 3 Toralf Förster 2024-04-08 17:14:57 UTC]

Created attachment 889826 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2024-04-08 17:14:58 UTC]

Created attachment 889827 [details]
environment

[Comment 5 Toralf Förster 2024-04-08 17:14:59 UTC]

Created attachment 889828 [details]
etc.clang.tar.xz

[Comment 6 Toralf Förster 2024-04-08 17:15:00 UTC]

Created attachment 889829 [details]
etc.portage.tar.xz

[Comment 7 Toralf Förster 2024-04-08 17:15:01 UTC]

The file size of ./files/logs.tar.xz is too big (1.3M) for an upload. For few weeks the link http://tinderbox.zwiebeltoralf.de:31560/23.0_musl-20240403-202925/var/tmp/tb/issues/20240407-224709-dev-dotnet_dotnet-sdk-8.0.102/files/logs.tar.xz is valid.

[Comment 8 Toralf Förster 2024-04-08 17:15:02 UTC]

Created attachment 889830 [details]
qlist-info.txt.xz

[Comment 9 Toralf Förster 2024-04-08 17:15:03 UTC]

Created attachment 889831 [details]
temp.tar.xz

[Comment 10 Maciej Barć 2024-04-08 20:16:22 UTC]

> Exception: No file descriptors available : '/var/tmp/portage/dev-dotnet/dotnet-sdk-8.0.102/work/dotnet-sdk-8.0.2/artifacts/tmp/Release/Symbols/runtime/obj/System.IO.FileSystem.AccessControl/Release/net8.0-windows/PreTrim/System.IO.FileSystem.AccessControl.pdb'

Please increase number of open file descriptors in the chroot.

For reference limits on my dev machine:

-t: cpu time (seconds)              unlimited
-f: file size (blocks)              unlimited
-d: data seg size (kbytes)          unlimited
-s: stack size (kbytes)             8192
-c: core file size (blocks)         0
-m: resident set size (kbytes)      unlimited
-u: processes                       135933
-n: file descriptors                500000
-l: locked-in-memory size (kbytes)  4194304
-v: address space (kbytes)          unlimited
-x: file locks                      unlimited
-i: pending signals                 135933
-q: bytes in POSIX msg queues       819200
-e: max nice                        39
-r: max rt priority                 95
-N 15: rt cpu time (microseconds)   unlimited

> fs.file-max = 500000

[Comment 11 Toralf Förster 2024-04-08 20:18:23 UTC]

Hhm:

$ sysctl fs.file-max 
fs.file-max = 13180657

[Comment 12 Maciej Barć 2024-04-08 20:19:42 UTC]

(In reply to Toralf Förster from comment #11)
> Hhm:
> 
> $ sysctl fs.file-max 
> fs.file-max = 13180657

and what does "ulimit -a" say?

[Comment 13 Toralf Förster 2024-04-08 20:20:23 UTC]

(In reply to Maciej Barć from comment #12)
> (In reply to Toralf Förster from comment #11)
> > Hhm:
> > 
> > $ sysctl fs.file-max 
> > fs.file-max = 13180657
> 
> and what does "ulimit -a" say?

23-0-desktop-plasma-systemd-20240326-204505 ~ # ulimit -a
real-time non-blocking time  (microseconds, -R) unlimited
core file size              (blocks, -c) 0
data seg size               (kbytes, -d) unlimited
scheduling priority                 (-e) 0
file size                   (blocks, -f) unlimited
pending signals                     (-i) 514914
max locked memory           (kbytes, -l) 8192
max memory size             (kbytes, -m) unlimited
open files                          (-n) 1024
pipe size                (512 bytes, -p) 8
POSIX message queues         (bytes, -q) 819200
real-time priority                  (-r) 0
stack size                  (kbytes, -s) 8192
cpu time                   (seconds, -t) unlimited
max user processes                  (-u) 514914
virtual memory              (kbytes, -v) unlimited
file locks                          (-x) unlimited

[Comment 14 Maciej Barć 2024-04-08 20:22:39 UTC]

(In reply to Toralf Förster from comment #13)
> open files                          (-n) 1024

afaik this is the one it wants, and it is not propagated into your chroot

[Comment 15 Maciej Barć 2024-05-23 15:29:18 UTC]

*** Bug 932398 has been marked as a duplicate of this bug. ***