* 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.
* TM-51 Prep for reading and writing test results to artifactory.
* TM-51 Tests from target branch if no tests for current branch
* TM-51 Placeholder for test averaging over runs.
* TM-51 Replace slashes in branch names used as tags.
* TM-51 More placeholder work for the mean duration work.
* TM-51 Write out average tests results as as csv.
The csv file should grow and be updated on each run. This includes whether or not we are running unit tests, integration tests and so on.
* TM-51 Comment out old junit test archiving, add more comments.
* TM-51 Zip task needs to depend on a csv creation task.
If there isn't a csv file present, then the zip task doesn't run due to 'NO-SOURCE'
* TM-51 Zip task should ignore empty dirs
* TM-51 Fix up loading of test results.
We were looking for the wrong artifact name.
Add a bit more logging.
* TM-51 Fix up possible problem with allocating by class distribution.
If we encounter a class we haven't seen before, there won't be any tests.
This means we should give it some weight. '1' is far too small.
* TM-51 Test that we are definitely increment the run count.
Tracking down whether the zipped csv file should have incremented.
* TM-51 Better default value for missing test/class names.
Begin by using mean unit test duration, but we have the option to bump
that to the mean class unit tests duration.
* TM-51 More debug information around csv writing.
We should be incrementing the tests.
* TM-51 Reload the csv before updating it.
* TM-51 Reduce verbosity of logging.
* TM-51 Reinstate unit tests. Remove logging verbosity.
* TM-51 Load tests from artifactory in memory and avoid interim file.
* TM-51 Better handling of zero duration tests.
Ensure we return zero times from junit artifacts which may either be zero or have no recorded time. Before writing the tests duration csv file, store those with a known time, and then store those with zero using the average time.
* TM-51 Log whether we have recorded a test.
Tracking down the curious case where we seem to not be rerunning the
same set of tests on the second run.
* TM-51 Capture junit files as well.
Trying to track down whether some tests are intermittently run.
* TM-51 Change task dependencies to ensure ziptask is triggered.
* TM-51 Remove test assertion, and trigger build
* TM-51 Add corda/enterprise to artifactory tag name.
Moved properties to own file.
* TM-51 Remove unnecessary mean class-based duration.
* TM-51 Add more BucketingAllocator tests.
We need these to nail down its behaviour some more.
* TM-51 Further log information.
We don't seem to be finding the tests in the 'production' runs which is odd.
* TM-51 corda type double set?
* TM-51 do not set the project type in the properties.
SRP and all that.
* TM-51 better plan reporting
* TM-51 duration may be zero
Another runtime problem that doesn't show in tests.
* TM-51 better plan reporting
* fix missing space after image id
* fix merge issue in DistributedTesting
* TM-51 remove unused code when GET/PUT-ting to Artifactory.
* TM-51 put tasks in gradle group and tidy up zip task creation
* TM-51 Fix the junit XML path.
* TM-51 Fix the task graph
* TM-51 Less logging
Reapply change that was lost during merge - Adjust resolution of byteman jar to use java 11 compatible mechanism. - a1077092
Manual cherry pick of these changes (a1077092 + 3fafbe55)
Byteman is absent for most of the integration tests and long stacktrace is seen in the log
presently that un-necessarily attracts attention and consumes logging space.
(cherry picked from commit 2b6e59e7bd)
- Port ledger integrity work to `SingleThreadedStateMachineManager`
- Fix `StatemachineErrorHandlingTest`
- Fix compile errors in `RetryFlowMockTest` + `VaultObserverExceptionTest`
- Add method to `StaffedFlowHospital` that was missed during original merge
