Update module github.com/onsi/ginkgo/v2 to v2.2.0 #166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v2.1.3
->v2.2.0
Release Notes
onsi/ginkgo
v2.2.0
Compare Source
2.2.0
Generate real-time Progress Reports [
f91377c
]Ginkgo can now generate Progress Reports to point users at the current running line of code (including a preview of the actual source code) and a best guess at the most relevant subroutines.
These Progress Reports allow users to debug stuck or slow tests without exiting the Ginkgo process. A Progress Report can be generated at any time by sending Ginkgo a
SIGINFO
(^T
on MacOS/BSD) orSIGUSR1
.In addition, the user can specify
--poll-progress-after
and--poll-progress-interval
to have Ginkgo start periodically emitting progress reports if a given node takes too long. These can be overriden/set on a per-node basis with thePollProgressAfter
andPollProgressInterval
decorators.Progress Reports are emitted to stdout, and also stored in the machine-redable report formats that Ginkgo supports.
Ginkgo also uses this progress reporting infrastructure under the hood when handling timeouts and interrupts. This yields much more focused, useful, and informative stack traces than previously.
Features
BeforeSuite
,AfterSuite
,SynchronizedBeforeSuite
,SynchronizedAfterSuite
, andReportAfterSuite
now support (the relevant subset of) decorators. These can be passed in after the callback functions that are usually passed into these nodes.As a result the signature of these methods has changed and now includes a trailing
args ...interface{}
. For most users simply using the DSL, this change is transparent. However if you were assigning one of these functions to a custom variable (or passing it around) then your code may need to change to reflect the new signature.Maintenance
0ffde58
]896bbb9
]6d3a90e
]v2.1.6
Compare Source
2.1.6
Fixes
SuppressProgressReporting
decorator to turn off --progress announcements for a given node [dfef62a
]7373214
]v2.1.5
Compare Source
2.1.5
Fixes
6ad7138
]CurrentSpecReport
andAddReportEntry
are thread-safe [817c09b
]3cd8b93
]5cf23e2
] - even when only one spec has failedb1864ad
]219cc00
]71ebb74
]143d208
]b69554f
]Maintenance
e5dfce4
]7ae91c4
]e87a85a
]bbefe12
]9327906
]f44af96
]ef336aa
]v2.1.4
Compare Source
Fixes
when
when usingWhen
(this behavior was in 1.x but unintentionally lost during the 2.0 rewrite) [efce903
]a7bd1fe
]0976569
]aae4480
]f779385
]Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.