Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 923458 - dev-dotnet/dotnet-sdk-8.0.100-r2 fails to compile: hang
Summary: dev-dotnet/dotnet-sdk-8.0.100-r2 fails to compile: hang
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: dotnet project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-01 11:30 UTC by Agostino Sarubbo
Modified: 2024-02-01 13:12 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log,393.20 KB, text/plain)
2024-02-01 11:30 UTC, Agostino Sarubbo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2024-02-01 11:30:52 UTC
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-dotnet/dotnet-sdk-8.0.100-r2 fails to compile.
Discovered on: amd64 (internal ref: ci)

Info about the issue:
https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#CF0014
Comment 1 Agostino Sarubbo gentoo-dev 2024-02-01 11:30:55 UTC
Created attachment 883909 [details]
build.log

build log and emerge --info
Comment 2 Agostino Sarubbo gentoo-dev 2024-02-01 11:31:51 UTC
I can reproduce 100% of times
Comment 3 Maciej Barć gentoo-dev 2024-02-01 11:34:57 UTC
> Tinderbox killed the process after 3675 seconds (01h:01m:15s)

It takes way longer than 1h and 2m to emerge.

>  /var/tmp/portage/dev-dotnet/dotnet-sdk-8.0.100-r2/work/dotnet-sdk-8.0.0/artifacts/logs/vstest.log

It is deep into compilation process here.

Or is it a matter of that there is absolutely no activity for 1h **after** this line?:

> SOURCE_BUILT_SDK_VERSION_ARCADE=8.0.0-beta.23516.4
Comment 4 Agostino Sarubbo gentoo-dev 2024-02-01 11:39:07 UTC
It takes few seconds to arrive to the line:

SOURCE_BUILT_SDK_VERSION_ARCADE=8.0.0-beta.23516.4

then, after an hour there is no progress, but I don't know if it is doing something in the wild.
Comment 5 Maciej Barć gentoo-dev 2024-02-01 11:41:11 UTC
(In reply to Agostino Sarubbo from comment #4)
> It takes few seconds to arrive to the line:
> 
> SOURCE_BUILT_SDK_VERSION_ARCADE=8.0.0-beta.23516.4
> 
> then, after an hour there is no progress, but I don't know if it is doing
> something in the wild.

So that is the total time that it took to fail?

> but I don't know if it is doing something in the wild.

If you want to investigate you cna look into the latest log build process shows, that is: /var/tmp/portage/dev-dotnet/dotnet-sdk-8.0.100-r2/work/dotnet-sdk-8.0.0/artifacts/logs/vstest.log
Comment 6 Agostino Sarubbo gentoo-dev 2024-02-01 11:49:28 UTC
(In reply to Maciej Barć from comment #5)
> So that is the total time that it took to fail?

I don't know if I was unclear but:
1) you launch emerge
2) After 60 seconds it prints SOURCE_BUILT_SDK_VERSION_ARCADE=8.0.0-beta.23516.4
3) After 1 hour the build log is in the same state.

> If you want to investigate you cna look into the latest log build process
> shows, that is:
> /var/tmp/portage/dev-dotnet/dotnet-sdk-8.0.100-r2/work/dotnet-sdk-8.0.0/
> artifacts/logs/vstest.log

I relaunched the job, let's see what vstest.log says.
Comment 7 Maciej Barć gentoo-dev 2024-02-01 11:53:49 UTC
(In reply to Agostino Sarubbo from comment #6)

> SOURCE_BUILT_SDK_VERSION_ARCADE=8.0.0-beta.23516.4

I was refereeing to the last line before the process was killed.

Here you are talking about the first occurrence of "SOURCE_BUILT_SDK_VERSION_ARCADE=8.0.0-beta.23516.4".

So, again, last thing it prints is the above, then in sits there doing
nothing for an hour and is killed?
Comment 8 Agostino Sarubbo gentoo-dev 2024-02-01 11:58:09 UTC
(In reply to Maciej Barć from comment #7)
> So, again, last thing it prints is the above, then in sits there doing
> nothing for an hour and is killed?

yes
Comment 9 Agostino Sarubbo gentoo-dev 2024-02-01 13:12:40 UTC
I verified that it is not an hang but it's just the build log not updated. Feel free to reopen if you want to see this bug as improvement to print runtime.log into build.log