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

bug: Set thread names correctly on macOS and Linux #6627

Merged
merged 1 commit into from
Sep 5, 2020

Conversation

theopolis
Copy link
Member

Thread names are limited to 16 characters include the ending \0.

@theopolis theopolis added the bug label Sep 3, 2020
@theopolis
Copy link
Member Author

Heads up @Breakwell we might have a problem with the Windows sccache. I am unsure why the Windows CI failed here?

@Breakwell
Copy link
Contributor

Breakwell commented Sep 3, 2020

Heads up @Breakwell we might have a problem with the Windows sccache. I am unsure why the Windows CI failed here?

Taking a quick look I didn't update the submodule cache to have unique key for the build job: https://github.com/osquery/osquery/blob/master/azure-pipelines.yml#L314 so it's just "Windows" I guess this would fall with the pattern of the libradkafka failing (it's a submodule) I'll raise a PR with a change to making it unique to the architecture:

#6628

@Smjert
Copy link
Member

Smjert commented Sep 3, 2020

@Breakwell submodules are the same, doesn't matter if it's Windows 32 or 64, it's just a "git clone".
It's only the build cache that would change between the two.

@theopolis theopolis merged commit fc63cb6 into osquery:master Sep 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants