[
https://issues.apache.org/jira/browse/CASSANDRA-15234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487627#comment-17487627
]
Ekaterina Dimitrova edited comment on CASSANDRA-15234 at 2/6/22, 6:12 AM:
--------------------------------------------------------------------------
I received an email that travis has failed for cassandra-dtest. It shows me
that it failed with syntax error during execution pytest --metatests. I pulled
the latest ccm locally and reran that step. It completed fine, same with my
branch.
In the meantime I saw that I missed to refert to riptano/ccm in
requirements.txt. It seems it wasn't in the separate commit as I thought. I
just ninja fixed that and I am going to see whether travis will fail again.
Jenkins is still running, nothing unusual there for now.
was (Author: e.dimitrova):
I received an email that travis has failed for cassandra-dtest. It shows me
that it failed with syntax error during execution pytest --metatests. I pulled
the latest ccm locally and reran that step. It completed fine, same with my
branch.
In the meantime I saw that I missed to refert to riptano/ccm in
requirements.txt. It seems it wasn't in the separate branch as I thought. I
just ninja fixed that and I am going to see whether travis will fail again.
Jenkins is still running, nothing unusual there for now.
> Standardise config and JVM parameters
> -------------------------------------
>
> Key: CASSANDRA-15234
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15234
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Benedict Elliott Smith
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.1
>
> Attachments: CASSANDRA-15234-3-DTests-JAVA8.txt
>
>
> We have a bunch of inconsistent names and config patterns in the codebase,
> both from the yams and JVM properties. It would be nice to standardise the
> naming (such as otc_ vs internode_) as well as the provision of values with
> units - while maintaining perpetual backwards compatibility with the old
> parameter names, of course.
> For temporal units, I would propose parsing strings with suffixes of:
> {{code}}
> u|micros(econds?)?
> ms|millis(econds?)?
> s(econds?)?
> m(inutes?)?
> h(ours?)?
> d(ays?)?
> mo(nths?)?
> {{code}}
> For rate units, I would propose parsing any of the standard {{B/s, KiB/s,
> MiB/s, GiB/s, TiB/s}}.
> Perhaps for avoiding ambiguity we could not accept bauds {{bs, Mbps}} or
> powers of 1000 such as {{KB/s}}, given these are regularly used for either
> their old or new definition e.g. {{KiB/s}}, or we could support them and
> simply log the value in bytes/s.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
