Conversation
Signed-off-by: Harsh Vardhan <harsh.vardhan@mayadata.io>
Signed-off-by: Harsh Vardhan <harsh.vardhan@mayadata.io>
|
Could you please provide the testing done after the version upgrade? |
Fix: Prior Go 1.16, an os.Exit(0) was not considered as a Test failure. Ref: https://tip.golang.org/doc/go1.16#go-test
|
Please mark the PR for #SODACODE2022 in the description |
|
@vharsh Can you please look at the failing CI jobs |
I'm on it, it has broken from Golang 1.14 and it's lacking some metric Component name from the 15th metric, I'm trying to understand how the tests were passing all this while. |
|
@vharsh thanks... |
|
I did some debugging again this long weekend, sharing all what I've found. What factors are causing the Ceph metrics to fail?
Some errors only visible in the newer Golang v1.17 or v1.18 Things I need to look further:
|
|
@vharsh Thanks for debugging this, feel free to bump the go-ceph to newer versions. |
|
@vharsh Can you please look at @asifdxtreme suggestion and check further, thanks |
|
@sushanthakumar Yeah, I was investigating this last weekend, I'll take a look at it soon-ish. |
What type of PR is this?
/kind cleanup
#SODACODE2022
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #83
Test Report Added?:
/kind NOT-TESTED
Special notes for your reviewer:
Breaking changes
os.Exit(0)will now fail the unit tests.