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-arm in repository toolchain/ci/base-artifacts.
discards 3e4d398f24 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards 8c801045eb 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 119fe18fc1 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards 551827c2e8 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards 4972d05643 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 9da3e7c582 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards a028935bf2 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 3e4529c428 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards f302ff390f 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 2827f46425 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards b541589f01 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards a13245f5e2 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards c869860f00 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards 96301a6605 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards 6f3d7185fc 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 61b10fb1ae 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 67049d1875 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 6a92f5f6ac 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards 500748bd8c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards caa49a140c 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards bd49b2698b 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards d3dcffe4a3 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards d2e4279c4d 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards e836229f3a 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 30acc6acc5 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards 798dbb0e26 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 6fd8e16405 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards 2889be22d0 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards c28d73f0ae 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards d02ba42289 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 69393bc903 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards e36fd4ceb3 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 746677860e 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards c0c503d73c 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 5811dee359 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 5549fdfd82 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards aad2fa8ba8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards ad8ac2003f 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards dc93552753 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 2fbe25446b 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 8220377e86 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 8ebe72955f 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 99e44a0985 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 0ce509e092 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards e18a6b2a4b 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 9ceff035c7 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 0fa6edf7d1 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards fe99fcbe8d 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 2c55a5b161 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards e1aac778ad 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 181480f244 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 53b710be59 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 3418fa8dcb 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 8b8c1ee0b6 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards cb68038c99 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 4f71af4b6d 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards f302455f5e 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards fbfd013dd4 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 7f44d21ab7 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards c6864c5cf2 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 958bb1e71b 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards b7a4ac3707 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 28318ab1ea 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards bade21897f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards f8c2e1a15d 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards e10003f886 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 2252f6009a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards bde101c967 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards f6def69b7a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards a7888ce4e3 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards d63d2fa724 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards e168b85195 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards aade2441c0 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards a85722f874 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards dff3ca3cd7 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 8c627b3fd2 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 495b7d59ba 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards bc468c62bb 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards d569ac16e9 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 8b1a631ec4 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards f6ec4447c3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards deaf4b12a6 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 653102ecf3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 320aa17bca 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards bbcf96511b 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 49a037f6d0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 37ffc58ad7 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d229a91f03 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards d88684a0a7 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 81447a8a06 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards d1f946e0ba 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 24adfad8d5 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 338dbcb58d 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards a9908c54fb 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 3aefe07f41 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c74be6cbaa 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 9fea54a026 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 57c5f64a35 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 08a03e4348 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f5478e809d 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 25fb1d0b8f 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 16f57ec6ba 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3586943f17 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new d71b248254 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9811ca58b2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1848b34c43 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c5bdd37c25 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 7e3384b77c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new aa39cc3de6 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new df02d54a2c 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 7d177db72e 84: onsuccess: 1: Success after gcc/glibc: 9 commits new ca077594fa 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 97478aa1aa 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new d49bd63ca5 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 3b0b655070 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 7beb2c8180 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 387af364a3 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 92c31ca2ad 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new e805129db7 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 6ba2961e20 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 74e1da2a19 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 4bb8899c4d 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 0e177b2ce8 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 93c1c8a99a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new ff98e3c4b1 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new b8f9c8329c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 7f1deb99f1 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new d20076e6a3 101: onsuccess: #1693: 1: Success after glibc: 14 commits new f2cfcc046c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 67054ff742 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 5b6d8e661e 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 794f9a5ab1 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new a15356e312 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 05b85698ed 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new bdda373023 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 66620aa61c 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 9bd519c20f 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 3a33347fd5 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 42b89c2d00 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 254d16f899 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 4095567ad0 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 9ccb2d996f 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new d9b527e399 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new a1e1179bbe 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new eb01b6d4f8 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 0c7019a09a 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new bb0135941a 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 5fe6c723e8 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new b462f34f0e 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new fc7173909d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 9a1097df21 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 21f635e95f 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 82085ed7b3 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 4f6eaab3c5 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 6a0fef1e77 128: onsuccess: #1723: 1: Success after linux: 12 commits new 073bb14b25 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new f5bedc73d7 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 328d24f5d2 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new f0ca5fa1f4 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 308078faba 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new f820cb9ea0 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 89006ebbc1 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 8f880c7b38 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 33161bfaff 137: onsuccess: #1736: 1: Success after gcc: 5 commits new e463aa2bd3 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new dd2f362a79 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 8e3309cabd 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new b377eabe8f 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 4be13b0f5a 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 9d0e99fbfb 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 88ed180c7c 144: onsuccess: #1743: 1: Success after glibc: 2 commits new e7cd7217aa 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 19ef4c2962 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 2c81ef5f39 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 71602b5bc2 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new b5da136e71 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new d0ce863618 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new c501c95025 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 3b1d49995b 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 898694c20c 153: onsuccess: #1754: 1: Success after gcc: 2 commits new 4033b36bcc 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new fa0f705fa1 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 81ef1bd76e 156: onsuccess: #1757: 1: Success after gcc: 4 commits new 35ee93c2e7 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 300734af6f 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 98d1688e01 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new cf3399a510 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 2033a0902c 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new bbbccbb66e 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new bfdad8c07e 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new b9652e5f82 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new c6d8b0d176 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new e888b4d3e8 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new bc2dc88e7c 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new e4d22e7191 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new a0857af4df 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 91a8396746 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new ceb0871c59 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new d0d56c8b5d 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new b976d80937 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new d128675d4e 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new ae5a55e6ec 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new 163035dee8 176: onsuccess: #1791: 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 (3e4d398f24) \ 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 1684 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30552 -> 30252 bytes 04-build_abe-stage1/console.log.xz | Bin 90808 -> 90976 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8596 -> 9000 bytes 07-build_abe-glibc/console.log.xz | Bin 234256 -> 233984 bytes 08-build_abe-stage2/console.log.xz | Bin 223800 -> 224344 bytes 09-build_abe-gdb/console.log.xz | Bin 37980 -> 37424 bytes 10-build_abe-qemu/console.log.xz | Bin 31524 -> 31604 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2648 -> 2752 bytes 13-check_regression/console.log.xz | Bin 6116 -> 9484 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 55 + 13-check_regression/mail-body.txt | 120 +- 13-check_regression/results.compare | 95 +- 13-check_regression/results.compare2 | 350 ++- 13-check_regression/results.regressions | 90 + 14-update_baseline/console.log | 58 +- 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 | 122 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 90 + sumfiles/g++.log.xz | Bin 2656620 -> 2691384 bytes sumfiles/g++.sum | 269 +- sumfiles/gcc.log.xz | Bin 2208992 -> 2209072 bytes sumfiles/gcc.sum | 2654 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 887552 -> 885180 bytes sumfiles/gfortran.sum | 134 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201500 -> 201528 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 432632 -> 431184 bytes sumfiles/libstdc++.sum | 32 +- 48 files changed, 2572 insertions(+), 1604 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions copy dashboard/{squad => squad-vs-first}/score/results-functional.json (100%)