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

APC HID UPS: Add ability to set battery battery.mfr.date #1318

Merged
merged 1 commit into from Mar 8, 2022
Merged

APC HID UPS: Add ability to set battery battery.mfr.date #1318

merged 1 commit into from Mar 8, 2022

Conversation

WereCatf
Copy link
Contributor

Some APC UPSes allow for setting battery.mfr.date, so it can be
easily referenced later, even if there were no stickers or papers
left to refer to.

This patch has been tested to work with APC Back-UPS ES 550G.

Signed-off-by: Nita Vesa werecatf@outlook.com

@jimklimov
Copy link
Member

Looks good!

I'll be without a computer for a while, so sanity-checking: should that be a double type? Not a long like in snmp-ups for example?

@WereCatf
Copy link
Contributor Author

WereCatf commented Feb 28, 2022 via email

@jimklimov
Copy link
Member

jimklimov commented Mar 2, 2022 via email

@WereCatf
Copy link
Contributor Author

WereCatf commented Mar 2, 2022

@jimklimov You're probably correct: better safe than sorry. I have amended my commit; do let me know, if you want any more changes.

Some APC UPSes allow for setting battery.mfr.date, so it can be
easily referenced later, even if there were no stickers or papers
left to refer to.

This patch has been tested to work with APC Back-UPS ES 550G.

Signed-off-by: Nita Vesa <werecatf@outlook.com>
@WereCatf
Copy link
Contributor Author

WereCatf commented Mar 8, 2022

Is there a direct link to a logfile or something somewhere, so I could see what the CI-build failed at? The website never loads for me, no matter what I do. It just stalls and so I can't check what's going on.

@jimklimov
Copy link
Member

Unfortunately the sponsor-provided VMs behind NUT CI are quite weak or overwhelmed since the new-year migration, so it does take a while for Jenkins to render or to think a next thought :(

The website does open, at least for the legacy interface (cut the URL at build number) but indeed it can take a minute too. I'll take a look at making legacy UI the default there; the new fancy UI autorefresh kicks in before it renders the thing, it seems.

The build page should have links to specific logs of failed scenarios, primarily seek the "*.check.gz" files in the list; the general "console" log is too cluttered to make sense of usually.

@WereCatf
Copy link
Contributor Author

WereCatf commented Mar 8, 2022

If I'm reading that right, it seems the build failed because...the build-process got disconnected?

Build agent lost in flight

A build agent got disconnected (network issue, OOM on their host, other crash). Job should be restarted to see the "real" results of that build matrix combination.
[Indication 1](https://ci.networkupstools.org/job/nut/job/nut/job/PR-1318/lastUnsuccessfulBuild/consoleFull#-15882823778fad603d-05df-417f-bee1-2f432162d8a8)

@jimklimov
Copy link
Member

jimklimov commented Mar 8, 2022

"There is no cloud, just somebody else's..." (leftover) "...computers"
sigh :(

@jimklimov jimklimov merged commit 6d7b236 into networkupstools:master Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants