Brynjar Eide <brynjar@ip-only.no>: Author Summary

Builds triggered by Brynjar Eide <brynjar@ip-only.no>

Builds triggered by an author are those builds which contains changes committed by the author.
44
0 (0%)
44 (100%)

Breakages and fixes

Broken means the build has failed but the previous build was successful.
Fixed means that the build was successful but the previous build has failed.
0 (0% of all builds triggered)
2 (5% of all builds triggered)
2
Build Completed Code commits Tests
POWEREDBY › PBO2018 › #57 2 months ago
NMS-10410: Respect time zones and exclude future outages
Make sure not to include outages where the iflostservice starts after
the cut-off of the requested outage period.

In addition, all conversions and comparisons should respect the
time zone settings, to avoid problems during DST / Standard Time
transitions.
Calculate availability based on complete downtime
24 hour availability percentage per node requires the entire downtime
as a sum of all services' outage intervals.
NMS-10410: Let users override DS_TIME_RANGE_NUMBER
Both the user-definable 'TIME_RANGE' and 'DS_TIME_RANGE_NUMBER'
default to 7, but DS_TIME_RANGE_NUMBER was never initialized in
<datasetRun>.
Testless build
OPENNMS › DM › #580 2 months ago
NMS-10410: Let users override DS_TIME_RANGE_NUMBER
Both the user-definable 'TIME_RANGE' and 'DS_TIME_RANGE_NUMBER'
default to 7, but DS_TIME_RANGE_NUMBER was never initialized in
<datasetRun>.
NMS-10410: Respect time zones and exclude future outages
Make sure not to include outages where the iflostservice starts after
the cut-off of the requested outage period.

In addition, all conversions and comparisons should respect the
time zone settings, to avoid problems during DST / Standard Time
transitions.
Calculate availability based on complete downtime
24 hour availability percentage per node requires the entire downtime
as a sum of all services' outage intervals.
Testless build
OPENNMS › OPENNMS › #10 2 months ago
NMS-10410: Respect time zones and exclude future outages
Make sure not to include outages where the iflostservice starts after
the cut-off of the requested outage period.

In addition, all conversions and comparisons should respect the
time zone settings, to avoid problems during DST / Standard Time
transitions.
Calculate availability based on complete downtime
24 hour availability percentage per node requires the entire downtime
as a sum of all services' outage intervals.
NMS-10410: Let users override DS_TIME_RANGE_NUMBER
Both the user-definable 'TIME_RANGE' and 'DS_TIME_RANGE_NUMBER'
default to 7, but DS_TIME_RANGE_NUMBER was never initialized in
<datasetRun>.
7750 passed
POWEREDBY › MERGEPBO2018 › #169 2 months ago
Calculate availability based on complete downtime
24 hour availability percentage per node requires the entire downtime
as a sum of all services' outage intervals.
Testless build
PRIME › MERGE2018 › #185 2 months ago
Calculate availability based on complete downtime
24 hour availability percentage per node requires the entire downtime
as a sum of all services' outage intervals.
Testless build
POWEREDBY › MERGEPBO2018 › #164 2 months ago
NMS-10410: Respect time zones and exclude future outages
Make sure not to include outages where the iflostservice starts after
the cut-off of the requested outage period.

In addition, all conversions and comparisons should respect the
time zone settings, to avoid problems during DST / Standard Time
transitions.
NMS-10410: Let users override DS_TIME_RANGE_NUMBER
Both the user-definable 'TIME_RANGE' and 'DS_TIME_RANGE_NUMBER'
default to 7, but DS_TIME_RANGE_NUMBER was never initialized in
<datasetRun>.
Testless build
PRIME › MERGE2018 › #180 2 months ago
NMS-10410: Respect time zones and exclude future outages
Make sure not to include outages where the iflostservice starts after
the cut-off of the requested outage period.

In addition, all conversions and comparisons should respect the
time zone settings, to avoid problems during DST / Standard Time
transitions.
NMS-10410: Let users override DS_TIME_RANGE_NUMBER
Both the user-definable 'TIME_RANGE' and 'DS_TIME_RANGE_NUMBER'
default to 7, but DS_TIME_RANGE_NUMBER was never initialized in
<datasetRun>.
Testless build
You have insufficient permissions to see all of the builds.
Build Completed Code commits Tests
Build Completed Code commits Tests
OPENNMS › OPENNMS › #10 2 months ago
NMS-10410: Respect time zones and exclude future outages
Make sure not to include outages where the iflostservice starts after
the cut-off of the requested outage period.

In addition, all conversions and comparisons should respect the
time zone settings, to avoid problems during DST / Standard Time
transitions.
Calculate availability based on complete downtime
24 hour availability percentage per node requires the entire downtime
as a sum of all services' outage intervals.
NMS-10410: Let users override DS_TIME_RANGE_NUMBER
Both the user-definable 'TIME_RANGE' and 'DS_TIME_RANGE_NUMBER'
default to 7, but DS_TIME_RANGE_NUMBER was never initialized in
<datasetRun>.
7750 passed
OPENNMS › ONMS › #1493 10 months ago
NMS-10370: fix misleading INFO log message
NMS-10352: Fix type for some Cassandra JMX values
Changes type from 'gauge' to 'counter' for MemtableSwitchCount and
the DroppedMessage attributes, to match the JMX types.
7798 passed