Closed ff137 closed 1 month ago
K8s Test Coverage
Tests | Skipped | Failures | Errors | Time |
---|---|---|---|---|
1070 | 4 :zzz: | 0 :x: | 0 :fire: | 13m 0s :stopwatch: |
K8s Regression Test Coverage
Tests | Skipped | Failures | Errors | Time |
---|---|---|---|---|
1070 | 36 :zzz: | 0 :x: | 0 :fire: | 6m 50s :stopwatch: |
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
K8s Test Coverage
Tests | Skipped | Failures | Errors | Time |
---|---|---|---|---|
1070 | 4 :zzz: | 0 :x: | 0 :fire: | 11m 53s :stopwatch: |
K8s Regression Test Coverage
Tests | Skipped | Failures | Errors | Time |
---|---|---|---|---|
1070 | 36 :zzz: | 0 :x: | 0 :fire: | 4m 5s :stopwatch: |
Trust registry connections are established out-of-band, and therefore do not get the usual "alias" field that we can filter when we fetch records. So, we filter by "their_label" instead. This will only work if the regression-verifier tenant does not have many, many connections.
So this modifies logic to support the regression-verifier having up to 10'000 connections, and is therefore a temporary solution. A full solution should clean up temporary connections created in regression tests.