diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2021-11-15 17:27:15 +0100 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2021-11-15 17:27:17 +0100 |
| commit | 15d109802ab93b0af9647858c9d8adcd8a2db84a (patch) | |
| tree | 43dd4b67ac5317f8896ba1628b01f8625bb3a7de /contrib/verifybinaries | |
| parent | fa2303989bed629c1d6911034370db66c5485ce0 (diff) | |
| parent | 23c3dcb4e74b21c7a1f1bb334cb5547a6bf128f1 (diff) | |
Merge bitcoin/bitcoin#23513: ci: Drop --failfast in functional tests on native Windows CI task
23c3dcb4e74b21c7a1f1bb334cb5547a6bf128f1 ci: Drop --failfast in functional tests on native Windows CI task (Hennadii Stepanov)
Pull request description:
As it was [discussed](https://github.com/bitcoin/bitcoin/pull/22980#issuecomment-964073830) in bitcoin/bitcoin#22980:
> seeing _all_ of the failed tests can give us a useful hint for debugging (was thinking about that while reviewing and testing bitcoin/bitcoin#23300).
There is a [concern](https://github.com/bitcoin/bitcoin/pull/22980#issuecomment-964085922) about such approach:
> If there is a CI failure, it will be good to know the result as early as possible after opening the pull request.
But, [OTOH](https://github.com/bitcoin/bitcoin/pull/22980#issuecomment-964095026):
> the average amount of saved time for such an approach [using `--failfast`] is less significant than it could appear.
ACKs for top commit:
MarcoFalke:
cr ACK 23c3dcb4e74b21c7a1f1bb334cb5547a6bf128f1 seems fine to give this a try
Tree-SHA512: d28f5712b4edfdbcef48b0633017da9172cef1835bcea51eaeeabf15c133f6bb6888227afc130279c3899365a4fd0f200fb9b0c4cb1ff80f21cbc766b8907764
Diffstat (limited to 'contrib/verifybinaries')
0 files changed, 0 insertions, 0 deletions