[
https://issues.apache.org/jira/browse/CASSANDRA-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806261#comment-17806261
]
Stefan Miklosovic commented on CASSANDRA-16565:
-----------------------------------------------
Builds which passed the build job
j17
https://app.circleci.com/pipelines/github/instaclustr/cassandra/3768/workflows/dc383568-5db8-4823-b46a-c563afbbe949
j11
https://app.circleci.com/pipelines/github/instaclustr/cassandra/3768/workflows/4999137c-0352-47e5-8d93-291d978c1934
The thing which seem to fix the build problem is this (1), basically creating
that dir before we download any files into it. This really solves the problem.
I am not sure why this is happening and if this is a problem for other branches
as well and if we should not patch it first.
(1)
https://github.com/instaclustr/cassandra/commit/97135ce21b6c4e61a00c8d0c8e0c8218a7704f1a
> Remove dependency on sigar
> --------------------------
>
> Key: CASSANDRA-16565
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16565
> Project: Cassandra
> Issue Type: Improvement
> Components: Build
> Reporter: David Capwell
> Assignee: Claude Warren
> Priority: Normal
> Fix For: 5.x
>
>
> sigar is used to check if the environment has good settings for running C*,
> but requires we bundle a lot of native libraries to perform this check (which
> can also be done elsewhere). This project also appears to be dead as the
> last commit was around 6 years ago.
> With the move to resolve artifacts rather than commit them, removing this
> dependency would remove majority of the artifacts fetched from GitHub.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
