This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 202d8774df 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards e405efcf88 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards c38af139f9 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 5f95b7308d 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards b722228722 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 931deb5cff 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards f83af64af2 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 3543f72128 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards f873501e2d 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 5aa70db960 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 8282eb35ac 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 4ac278687f 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards b180d8567d 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 4a7e5e6f1b 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards fd87d7001b 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 1394c43443 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 785fa9f16b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 73e56aa0aa 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 69e7a39532 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards baded9400d 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 71e2980184 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards e0186f38ec 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 87a311925b 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards ae1cfcabd0 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards 6ea8bedc6b 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards d4eb458162 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 5544098cf2 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 3eea3b175c 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards f1c36e269a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 4ca2fef580 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 1555df62c5 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards f53f7276a8 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards ed2f59dfa6 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 54dc3b769e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 6d7118e39f 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 9003597a4d 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 344f852c0e 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 4a685d5495 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards c984aed774 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards e37a7c3ffa 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 43264a1f7b 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 8313847b31 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 67594c5078 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 9e576be037 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards c548940ec2 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 512c1e87b4 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards c1aaa1a202 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards a6c892fc5b 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 50d65417af 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 0e6729a30b 128: onsuccess: #2163: 1: Success after linux: 23 commits discards fb4988aeff 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 03de3d50e0 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards fe033e7896 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards d13464a4de 124: onsuccess: #2159: 1: Success after linux: 23 commits discards d3908de23f 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards a6cbd98d74 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards c9aaa3a76d 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 03baa9368a 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards fd2b14c14f 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 3b5d248844 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 1cb3821203 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 61ae6c428b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards a486eee2ef 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards a5671ab8c4 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards fc519d413c 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8cfb8f8a52 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 072847d0d0 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards a5585a0179 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 7aa2c22165 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 4fd60c3cc4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 6b1572d10d 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 0f16dd621f 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards b6baa39fb6 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards ca859bc6c5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 2216852a9b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 848d3e334a 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards bb728033bf 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards f3c9c31e7c 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards bbe627138f 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards d04bea00bb 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards c2186e7398 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 1e25e8c42f 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 1a45308ed5 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 594c19f8f5 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards fa73eae87a 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 136de1e7dc 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 746689909e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards c0043cafcc 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards caa037ed8d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 46fd6a46c2 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards d095f3d3d0 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 0ca0f15e88 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards f65b4ad853 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards a99138df2e 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards ce582a9267 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 282d176f7c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d390159fd2 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 0a1f988dee 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b50991bf43 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 478799528a 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 81c8430e17 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 6d0066368f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new bbf8897a79 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 59b7536566 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 603eb9eb43 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a5c98ea97c 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 0b67b906bc 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 3cbe04a504 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new f63df8cdc1 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new d22a3510ea 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 433dadb65a 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 971d404bee 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 702c731fbf 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 1b773b1db5 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 8f0c56c055 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 4f0e328fcc 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 44853dc61b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6b70bc4fd4 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new ea7233ebc0 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 08b0dee645 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 80d8f66a1a 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 287bde0d09 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 56bcdd4243 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 5d52fa7197 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 67253a8746 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new af9b2281e5 101: onsuccess: #2130: 1: Success after binutils: 81 commits new f8582b6f0b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new a7eef1b58d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new eb9f7ebdc3 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 95b50c96ee 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 52ddb911f3 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 56657a7720 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 24b020c463 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 649be33574 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new a7ea7e4481 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 0f8337a53d 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 604aed54a0 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 4f104a97cd 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 88fb918d72 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 01a6741cc2 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new fb782813df 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new bc664c6ce7 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new e100de033e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new e253333fb1 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 7343097423 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 2124d052c3 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new e46da7073e 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 3433f3a1d6 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new c42a2565cd 124: onsuccess: #2159: 1: Success after linux: 23 commits new 7b45685545 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 747ef3f036 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 692fd15d4d 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 29dc90400f 128: onsuccess: #2163: 1: Success after linux: 23 commits new 35c2d14d96 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 68159f4cac 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new a60d736051 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new db55c27560 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 119e3c98cd 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new a096fc44d1 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new b955be125c 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new d15204685c 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new ec28bb362e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 02f86bd504 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new c08d260eeb 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 3bc9c1ca39 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 154b242f5a 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 24ff2f28ea 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 8c8ce9a89e 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 4b13c6ee3f 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 6965a11cbb 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 5fab152da5 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 545099ab2c 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new d9f997227f 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 4793452a63 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 89ced19d3a 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 98e19edc16 151: onsuccess: #2186: 1: Success after gcc: 2 commits new c3341dffc3 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 93afa7320b 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 6dc89eb77a 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new d447b100d7 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 0355975c36 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 3c52daee51 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 0165f7b116 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new b994eb506b 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 9d871cd282 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 712ca4a7e8 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 9de70dc6d3 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new 4e4f34745e 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new abcc38b52b 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new b6b0d3ffbe 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 4e8022c949 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 1a71222bd1 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new b9018c5676 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new aeffc4a9a8 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new f335abbcdf 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new d2626d9ed5 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new ccaff6cee2 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new cc7a5afaac 173: onsuccess: #2208: 1: Success after gcc: 10 commits new bf9e7ee6b6 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new a8975b60e9 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new e686b1818c 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 28b6957fe4 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new a7a6fc434d 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...]
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (202d8774df) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1716 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30876 -> 30684 bytes 04-build_abe-stage1/console.log.xz | Bin 73548 -> 72916 bytes 06-build_abe-linux/console.log.xz | Bin 9168 -> 8756 bytes 07-build_abe-glibc/console.log.xz | Bin 240512 -> 240472 bytes 08-build_abe-stage2/console.log.xz | Bin 204252 -> 203252 bytes 09-build_abe-gdb/console.log.xz | Bin 38004 -> 37212 bytes 10-build_abe-qemu/console.log.xz | Bin 32008 -> 32464 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3932 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3680 -> 2840 bytes 13-check_regression/console.log.xz | Bin 5692 -> 14308 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 194 +- 13-check_regression/mail-body.txt | 143 +- 13-check_regression/results.compare | 212 +- 13-check_regression/results.compare2 | 1662 +++++- 13-check_regression/results.regressions | 102 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 12 +- dashboard/dashboard-push.sh | 5 + .../score/results-functional.json | 0 git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/dashboard-push.sh | 5 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 102 +- sumfiles/g++.log.xz | Bin 3413608 -> 3415380 bytes sumfiles/g++.sum | 62 +- sumfiles/gcc.log.xz | Bin 3031992 -> 3014812 bytes sumfiles/gcc.sum | 5810 +++++++++----------- sumfiles/gfortran.log.xz | Bin 1035388 -> 1029312 bytes sumfiles/gfortran.sum | 96 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202480 -> 202328 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428752 -> 421428 bytes sumfiles/libstdc++.sum | 8 +- 47 files changed, 5134 insertions(+), 3530 deletions(-) copy dashboard/{squad => squad-vs-first}/score/results-functional.json (100%)