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

The "build info" string included in libcoreclr.so contains invalid data #7829

Closed
mellinoe opened this issue Apr 6, 2017 · 2 comments
Closed
Labels
area-Infrastructure-coreclr backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity

Comments

@mellinoe
Copy link
Contributor

mellinoe commented Apr 6, 2017

We embed some build information in libcoreclr.so (and other binaries, I think), including the version, the commit hash, and the name of the build machine (presumably). It looks like at least some of our build machines are not able to run the hostname command, which leads to this incorrect output:

strings libcoreclr.so | grep "@(#)"
@(#)Version 4.6.25206.02 built by: root-/tmp/tmp5dc91113a4d04cb8b90399c24cabee67.exec.cmd: line 2: hostname: command not found. Commit Hash: f9d0333d8955c11a2e8f495f0a12d6384fb95541

root-/tmp/tmp5dc91113a4d04cb8b90399c24cabee67.exec.cmd: line 2: hostname: command not found.

The important information (commit hash) seems to be fine, at least.

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@msftgits msftgits added this to the Future milestone Jan 31, 2020
Copy link
Contributor

Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

This process is part of our issue cleanup automation.

@dotnet-policy-service dotnet-policy-service bot added backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity labels May 12, 2024
Copy link
Contributor

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.

@dotnet-policy-service dotnet-policy-service bot removed this from the Future milestone May 26, 2024
Infrastructure Backlog automation moved this from Future to Closed May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Infrastructure-coreclr backlog-cleanup-candidate An inactive issue that has been marked for automated closure. no-recent-activity
Projects
Status: Done
Development

No branches or pull requests

2 participants