build(deps): bump golang.org/x/net from 0.7.0 to 0.17.0 in /tests #658
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.7.0 to 0.17.0. - [Commits](golang/net@v0.7.0...v0.17.0) --- updated-dependencies: - dependency-name: golang.org/x/net dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
There was a problem hiding this comment.
The change should be fine and should not affect anything.
I tried running the tests, but as before in #681 and on the main branch, TestHistory/HA fails on my local setup, even as it works in the GitHub Action.
--- FAIL: TestHistory/HA (146.65s)
--- FAIL: TestHistory/HA/Acknowledgement (0.92s)
--- FAIL: TestHistory/HA/Acknowledgement/Consistency (0.00s)
--- FAIL: TestHistory/HA/Comment (61.34s)
--- FAIL: TestHistory/HA/Comment/Consistency (0.00s)
--- FAIL: TestHistory/HA/Downtime (62.37s)
--- FAIL: TestHistory/HA/Downtime/Consistency (0.00s)
--- FAIL: TestHistory/HA/Flapping (2.76s)
--- FAIL: TestHistory/HA/Flapping/Consistency (0.00s)
--- FAIL: TestHistory/HA/Notification (5.48s)
--- FAIL: TestHistory/HA/State (1.45s)
--- FAIL: TestHistory/HA/State/Consistency (0.01s)
But due to the fact that it works in the GHA and also the main branch fails for me, this should be fine.
|
That test case checks if both Icinga 2 masters produce a consistent history stream. I've seen that error a few times in GHA as well in the past. It could either be a problem in Icinga 2 (i.e. indeed generates inconsistent history) or the integration tests (like doesn't wait long enough for an event to happen, so far, I've only seen events missing completely in the full output, so it could just have taken a moment longer until it was emitted on the other master). Anyways, if you can reproduce this more reliably, we might have a chance to solve that mystery. But all of this doesn't seem to be related to this PR indeed. |
julianbrost
deleted the
dependabot/go_modules/tests/golang.org/x/net-0.17.0
branch
|
FTR, bumping the |
Bumps golang.org/x/net from 0.7.0 to 0.17.0.
Commits
b225e7chttp2: limit maximum handler goroutines to MaxConcurrentStreams88194adgo.mod: update golang.org/x dependencies2b60a61quic: fix several bugs in flow control accounting73d82efquic: handle DATA_BLOCKED frames5d5a036quic: handle streams moving from the data queue to the meta queue350aad2quic: correctly extend peer's flow control window after MAX_DATA21814e7quic: validate connection id transport parametersa600b35quic: avoid redundant MAX_DATA updatesea63359http2: check stream body is present on read timeoutddd8598quic: version negotiationDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.