* fix merge issue with sidecar image work
* add logic to refresh token in GKE
* set streaming to true
* set streaming to true
* set streaming to false, and increment number of workers for regression test as approaching 1h limit
* set PR build to run unit and integration tests
* try method distribution to see if faster
* rename test stage to reflect the fact it runs unit tests
* remove commented out parallel unit test code
* NOTICK: Mention platform version change in release notes (#5721)
Update the release notes to mention the platform version change.
* NOTICK: Mention platform version change in release notes
Added mention of preserved wire stability and compatibility across different versions.
* Typo fixes
* Corrected typo in release notes.
* Reworded change according to feedback - greatly simplified it.
* Slight rewording
* TM-88 only write the test to the file if it passes otherwise retry
* TM-88 1 failing test for testing purposes
* TM-88 fail an integration test instead of unit test
* TM-88 include failed test for retry
* TM-88 new logic for retrying failed tests
* TM-88 refactored to use retry class when dealing with test failures + copy results even after pod failure
* TM-88 remaining pods as set to prevent duplicates, limit retries to prevent crashed build and a bit more logging
* TM-88 atomic int instead of int array
* TM-88 moving atomic int outside retry loops
* TM-88 removing second retry as it is not needed
* TM-88 small fix to final copy
* TM-88 while loop to prevent destruction of results on test retry
* TM-88 removing shutdown hook
* TM-88 reverting to previous implementation
* TM-88 copying xml files before retry
* TM-88 removing fail
* TM-87 printing remaining pods on pod completion
* TM-87 extra commit to unblock jenkins?
* TM-87 extra commit to unblock jenkins?
* TM-87 pr comments
* NOTICK: Updated release notes for 4.3 (#5692)
Updated release notes for 4.3
* Clarification for old CI vs new CI
* Updated release notes
* Fixed broken links
* Addressed comments
* Added link
* Removed issues without a JIRA link
* Word change
* One more
* Mention deprecation of API
* Added Deprecations notice
* Moved confidential identities deprecation note
* TM-84 create intersection between includes and excludes and remove the intersection from the includes, that way we only print relevant exclusions instead of creating noise
* TM-84 add all instead of copy
* TM-84 remove xml from saved artifacts
* TM-84 reverting to default code to investigate behaviour
* TM-84 fixed intersection implementation
* TM-84 more logging to understand behaviour
* TM-84 more debugging
* TM-84 adding wildcard so contains works as expected
* TM-84 tweaking intersection closure
* TM-84 tweaking intersection
* TM-84 small change
* TM-84 suffixing wildcard
* TM-84 finishing up PR
* TM-84 PR comment
* TM-89 creating log outside of temp folder
* TM-89 reverting build.gradle changes now that the practical test worked. logs for each container can be viewed in the artifacts section
* Quick and dirty change to stop "Unable to start notaries." error message (#5686)
"Unable to start notaries. A required port might be bound already" is
returned whenever a startup error occurs while starting the notary nodes
in driver tests. This hides the real error.
This change prints the actual error to std_err and read from file
at a later point. This means the real error is not lost and will be
shown in failed builds.
* Suppress detekt warnings
This is to potentially help with debugging in the future as the
`flowId` could become confusing for received messages where the `flowId`
has nothing to do with the current flow.
* TM-74 Converting ParallelTestGroup
* TM-74 private fields, getters, distributedTesting refactoring
* TM-74 More conversions
* TM-74 reinstating ListTests groovy class
* TM-74 extracting enum and clas from ListTests
* TM-74 switching to java ListTests
* TM-74 null check
* TM-74 new access modifiers
* TM-74 minor changes
* TM-74 scrapping the conversions of ListTests to java
* TM-74 reverting build.gradle
* TM-74 formatting main gradle
* TM-74 removing the commented out code. It has been linked in the jira
* TM-74 adding list tests back for investigation
* TM-74 collecting after every operation
* TM-74 collecting after every operation
* TM-74 more debugging
* TM-74 more debugging with lifecycle now
* TM-74 debugging on the existing groovy file
* TM-74 with stream output
* TM-74 switching back to java
* TM-74 reverting java code, fixing cast in distributed testing file?
* TM-74 nailing down the line causing the problem
* TM-74 casting
* TM-74 changing types
* TM-74 stacktrace at pod lvl
* TM-74 stacktrace at pod lvl
* TM-74 fix issue with immutable list
* TM-74 reverting changes now that fix is in place
* TM-74 switching to generic task
* TM-74 turning off debugging
* TM-74 allocating by method
* CORDA-3350: Increase size of constraints column (#5639)
* Detekt
* Update api file with new threshold
* Add check in transaction builder
* Revert "Add check in transaction builder"
This reverts commit ca3128f44c.
* Add check for max number of keys
* Update api file
* Address Tudor's comments
* Remove check for pre-5 and add test for EC keys
* fix typo and rename liquibase script
* updated docs with measurement numbers for composite keys
* Make detekt happy again
The first run of any new branch will not find a corresponding tests.csv
and will return 404 not found which is fine. We do not need to display
the callstack at warning level.
