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_build/master-arm in repository toolchain/ci/base-artifacts.
discards cab8cd8ba6a 220: force: #1948: 5: Success after gcc: 4 commits discards 7b197389021 219: onsuccess: #1945: 5: Success after binutils: 8 commits discards a6c90ac00d7 218: onsuccess: #1943: 5: Success after gdb: 3 commits discards 0c5e5da97ec 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943 [...] discards 8350cdf4a15 216: onsuccess: #1940: 7: Success after linux: 12 commits discards 8ea95a2361a 215: onsuccess: #1938: 7: Success after gcc: 4 commits discards b2de327c509 214: onsuccess: #1937: 7: Success after binutils: 4 commits discards a9b94302a27 213: onsuccess: #1935: 7: Success after gcc: 2 commits discards 113abed30d0 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards e8e79004845 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/ [...] discards 1e96b54ceab 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 [...] discards e92394d9cb2 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/ [...] discards 15cb529f7c7 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards 019279e5302 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] discards 07feeebd736 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] discards dea48dbe376 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] discards 7e3f0a5d7b2 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] discards aad6cd024bc 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] discards e2ba54d4281 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] discards 4a7389c914c 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] discards 819095822b6 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] discards 2be8ae644ba 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] discards 24042e63da1 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] discards 988a3e0b17f 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] discards db9ea49edbb 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards 4eaebca3dea 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] discards d41e87b843c 194: force: #1853: 7: Success after gcc: 26 commits discards 96d4dc0153e 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] discards 9773f19eb49 192: onsuccess: #1848: 7: Success after linux: 213 commits discards ee0e7faf665 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 4fabb7800d4 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 7b458ccfc5d 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] discards 64a8138550d 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] discards ebc04f1e818 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] discards 5722c8a0832 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] discards 7587e197e38 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] discards 4daba121a45 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] discards dc4cdcc223d 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] discards 57507cda934 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] discards 5f7dcd3e579 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] discards 7a70584be04 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] discards 72a7448045d 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] discards d062f34011f 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] discards 667a9a8f2c7 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] discards 8892f17c111 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] discards 4cb36cb0ebd 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] discards 1e83bc9ed80 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] discards 5224a7f288a 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] discards 779f1c92c81 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards 3bfce488482 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] discards ebf2fb697ab 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] discards 031c64b27a8 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] discards 4e1def5820b 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] discards 9180cbd5065 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards f2814430eaa 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] discards 9d7d0122cb0 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] discards 4d974f4353e 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] discards 179f4992633 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] discards bb21b33ebf1 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] discards c783330d8e0 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] discards dcfdda6a785 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] discards 226731f9c21 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] discards 0badc692112 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards 9bee625f50c 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 3d1f7e5a527 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 659d30af08b 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] discards b7135050224 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] discards 7158f7c7fb8 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] discards da23e6a2ef2 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] discards 2eb6e3a6178 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] discards b4b2ef222e2 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] discards eb6bf9e3858 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] discards d2112d1349a 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards d28876b6bea 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] discards e135813e9fc 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] discards 6e46512bb40 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] discards 56dde14070b 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] discards 4ad9cbf155e 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] discards 1851543d460 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] discards 7fb2bde5ac9 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards d165301e5e8 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] discards 40dc05ebc6d 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards e58230ae2ca 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] discards 841f4f1c729 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] discards 01016edd503 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 9fedc00e4c4 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] discards db47545a41f 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 1 [...] discards fcc040d2a90 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/ [...] discards 9328a05ecbe 132: onsuccess: #1645: 7: Success after linux: 23 commits discards e5e66119107 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 1098090ce82 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/ [...] discards bd62b489a21 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards d6bb65f41a2 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 [...] discards 5a326fc46e1 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 73ba4e1a75c 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/ [...] discards 56c1cddd04a 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/ [...] discards c263cbc8a88 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/ [...] discards 27d73812edb 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] discards 4112cf617ff 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/ [...] discards 5335923f3e3 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 1 [...] discards 085a07b51c9 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qe [...] new 32bdce73b53 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qe [...] new 27cec101f7e 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 1 [...] new 61515d38a42 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/ [...] new 0b50e09ef4c 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] new a4371f1646d 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/ [...] new f09e5a1edaa 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/ [...] new 746c6fb0af0 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/ [...] new ce7b1733e01 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 617a2ba5306 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 [...] new e350b103211 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 713be0f166f 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/ [...] new 46821820d11 131: onsuccess: #1644: 7: Success after gcc: 10 commits new b90ce908691 132: onsuccess: #1645: 7: Success after linux: 23 commits new fcfef6774e3 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/ [...] new aaa868fb35d 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 1 [...] new 07bb05df6d4 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 2 [...] new e96bf657d26 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 2e8c980e992 137: force: #1652: 7: Success after basepoints/gcc-13-2870- [...] new 03d9d45bda2 138: force: #1653: 1: Failure after basepoints/gcc-13-2871- [...] new e9ea9c5c565 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 0d3949e1cdc 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/ [...] new 5cd4a2d0f85 141: onsuccess: #1656: 7: Success after gcc: 7 commits new a76136105cc 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/ [...] new 318e4e85431 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/ [...] new ef80a36af7f 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 [...] new c25b5a0ebce 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 1 [...] new cebaef381cb 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/ [...] new 2cfaf6eaf04 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/ [...] new 43cacdce625 148: onsuccess: #1663: 7: Success after glibc: 2 commits new f06a3719d5c 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 3 [...] new 9d8933e6629 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/ [...] new 720ced900de 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/ [...] new c52b0f78d2a 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/ [...] new 7d7da95542b 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 2 [...] new 560b2ba965a 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/ [...] new 86e7bf14f3a 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/ [...] new 830a6dd9153 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 58086e7f229 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 233cb9b3401 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 85a778632b5 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/ [...] new 9d5c73da83d 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 1 [...] new 8c65d7ccefd 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/ [...] new a9b219f084a 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/ [...] new 38c4e360a7b 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 [...] new da9be327558 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 1 [...] new 2047f236e54 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/ [...] new c7e91fde787 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/ [...] new 22bdca353fc 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 56ef2f3a7b7 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 3 [...] new 8352a1dadaf 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/ [...] new 6ddeadcdc51 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/ [...] new f17586d61c0 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/ [...] new 0cd81e9048e 172: onsuccess: #1687: 7: Success after gcc: 11 commits new 2ac1f1ac470 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qem [...] new 1fb10268b5a 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/ [...] new 19a3b71e1cb 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 1 [...] new c7ec995e63e 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/ [...] new 4f00a0e0847 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/ [...] new 16020ceb8b9 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/ [...] new fcb500f5d49 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/ [...] new f78da9536f9 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/ [...] new 8d82f1e1b28 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/ [...] new d77cd3cbabf 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 [...] new e3955fb3674 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/ [...] new 8ff39e8201a 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/ [...] new 7b17cee8c68 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/ [...] new 6345a5cbf45 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/ [...] new 78d9ec4e70a 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/ [...] new a18120eb430 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/ [...] new 1216fd104d5 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/ [...] new bca9f4a919c 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 69d4f5e7437 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 9c28730d0f5 192: onsuccess: #1848: 7: Success after linux: 213 commits new 4c9c5a3dfb0 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint- [...] new 6c65e83048c 194: force: #1853: 7: Success after gcc: 26 commits new 4371ac7fc29 195: force: #1854: 4: Failure after basepoints/gcc-13-3918- [...] new 5974eb79fec 196: onsuccess: #1855: 4: Success after gcc: 30 commits new cb501e30d5d 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/ [...] new db2a6eef828 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/ [...] new 0e01db373ee 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/ [...] new 25df45a046e 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/ [...] new ff025d19bb9 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/ [...] new b540b322fbb 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/ [...] new 98809d54114 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 1 [...] new f9d73da0dba 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 1 [...] new 6f73a7115eb 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 4 [...] new c0d01046692 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/ [...] new 791fb94e6ff 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 2 [...] new 7c4c8a0f95b 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new a723fb90054 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/ [...] new 5a96cc4a240 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 [...] new e227480ad40 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/ [...] new 5c2d7f3020a 212: onsuccess: #1934: 7: Success after gcc: 3 commits new e3ab8c4e9e0 213: onsuccess: #1935: 7: Success after gcc: 2 commits new 9fa0995954c 214: onsuccess: #1937: 7: Success after binutils: 4 commits new 4e4f9947ba6 215: onsuccess: #1938: 7: Success after gcc: 4 commits new fa17bce7ca5 216: onsuccess: #1940: 7: Success after linux: 12 commits new 2b508574e70 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943 [...] new 302ce61e402 218: onsuccess: #1943: 5: Success after gdb: 3 commits new 2b8ce9969be 219: onsuccess: #1945: 5: Success after binutils: 8 commits new 24fdc08120e 220: force: #1948: 5: Success after gcc: 4 commits new 9f2f2d7f0a4 221: force: #1949: 3: Failure after basepoints/gcc-13-4492- [...]
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 (cab8cd8ba6a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]
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 1748 -> 1656 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 31920 -> 31744 bytes 05-build_abe-stage1/console.log.xz | Bin 91804 -> 92236 bytes 07-build_abe-linux/console.log.xz | Bin 8600 -> 8508 bytes 08-build_abe-glibc/console.log.xz | Bin 238772 -> 173836 bytes 09-build_abe-stage2/console.log.xz | Bin 228692 -> 0 bytes 10-build_abe-gdb/console.log.xz | Bin 34644 -> 0 bytes 12-check_regression/console.log.xz | Bin 2864 -> 3724 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 13 +- 12-check_regression/mail-subject.txt | 2 +- 12-check_regression/results.regressions | 7 + 12-check_regression/trigger-bisect | 2 + 12-check_regression/trigger-notify | 0 13-update_baseline/console.log | 40 ++--- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 282 ++++++++++++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 13 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +-- results | 11 +- 28 files changed, 357 insertions(+), 54 deletions(-) delete mode 100644 09-build_abe-stage2/console.log.xz delete mode 100644 10-build_abe-gdb/console.log.xz create mode 100644 12-check_regression/results.regressions create mode 100644 12-check_regression/trigger-bisect create mode 100644 12-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh