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 85bf2d8326 194: force: #1853: 7: Success after gcc: 26 commits discards a1a439ffaa 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] discards af01c24765 192: onsuccess: #1848: 7: Success after linux: 213 commits discards da84fbf16a 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 028d83b8fa 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 36706900d2 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] discards 4c56ee02f6 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] discards 2c47087b0c 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] discards 1ee09f4492 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] discards 2155f94d3a 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] discards 2554d9b012 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] discards 5dfbf9b22c 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] discards 66dd34d7b8 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits discards 1f68e3bda2 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] discards 9fd12a9488 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] discards a9c303c2b4 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] discards c35c3b10c3 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] discards 4f6d96d245 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] discards 8608273765 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] discards d2328804a8 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] discards 3beb615abf 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] discards 6f42d62c88 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] discards 67675381aa 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards 20bd534e64 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] discards 334d71eff9 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] discards cd552a65dc 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] discards 1e4dc4f39a 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] discards 4663f2e318 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 4f5ebf1804 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] discards 0767be5712 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] discards 5361ae9096 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] discards c257713470 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits discards 45f8ac8ee1 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] discards 94ef1bcee6 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] discards 0413de9af9 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] discards a302b3c495 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards 41a1fd00d6 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards f9aea08432 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 5e3a6610d7 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards d895fbe2de 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards c00bae79d4 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 5ec6d48439 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards ba4c87d6a0 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards c69114194e 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 696ed533f9 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 78c494750b 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 6a8f7b212f 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 51dc75892b 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards bc64b923b8 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards 52afb5483d 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 569aaed52f 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 519c3f92f3 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 11bec708d7 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards 1c0509c8ce 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards b29d8d0969 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards c6f2257cce 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards fb27313251 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards f6e2df78f9 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 04f06cccae 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 885bd4af90 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 48547de702 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards e27f8bb9fd 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards ec2bb3a9d8 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 13114e40e8 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards a43729e21b 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards b5d5a7a4e2 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 0e3fcedd93 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 9821287572 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 64446f221a 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 7cd4eccdeb 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards dfe938af32 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 73d7d4d469 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 04a77dbd21 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards e65bc1678e 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 6b4e704ac0 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 57cf20653c 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 6e505c2683 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards 348ebd9825 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards e46133c9a5 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 128aee015e 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards b8c84f6286 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 3234df584c 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 01f1a3e493 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 1cc4292379 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards b8afa5dde8 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 9981faeb5f 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 8600196291 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 0fa9661161 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards ddae9da6d7 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards 27e1598f68 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 38821e9b61 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards cb2b6bfff5 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 4aa1b3bdbc 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards ad136114b4 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 502d02d4a3 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 3720149552 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards df4d992b93 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 28a2e07c57 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards e443c5671c 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards be29d655d4 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 981e57e181 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 3d2f70d001 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new fb58d7638b 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new aaf683a1ee 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new c0e96aef36 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 563a2e6ab3 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 44978d2987 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new ac002067c7 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 0e3ce92da7 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 1df75c3685 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new d9570d5406 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 5b2b406eef 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new d672446229 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 7524524b6b 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 13e69dd028 107: onsuccess: #1618: 7: Success after gcc: 2 commits new b2ca67beb9 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new a33208ad59 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 39ced6b935 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new c5b887a093 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 41a43dbf47 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 7944e5d4fa 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 23c5b574f9 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 9192c75ba4 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new bc90f3f6a7 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new e62ca6ded2 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 665a30f379 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 2a77a4868f 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 9e62c4ea1b 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 2260c32749 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new fc63dcfa89 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 494e2b3b37 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 4a1d306a65 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 2036686e25 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 255d5f9fb5 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 7d24372614 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 55c803329e 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new e5f9c0006e 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new c6f349a1b7 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 5adc9e6b1a 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 7e3659c2db 132: onsuccess: #1645: 7: Success after linux: 23 commits new 9b40e94213 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new a8083e80c0 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new 33dfef1c3f 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 0a9b6b2c7b 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 618d768cd5 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new fdc6f871bf 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new ede5a4239c 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 8aefe22ffb 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new d08d3d31ac 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 4dd8182dda 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new 04e5a0c9f9 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 5cd7135089 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new d9a787cc7b 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new c2ffd65205 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new 03c6ad700f 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 496dd146c4 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 6b8f281c08 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 18e1db2e6f 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new df1b45579e 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new 15fb2401a2 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new 3a55f73a21 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new dbd6e0e59e 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 8391576780 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new 9b92bb1848 156: onsuccess: #1671: 7: Success after gcc: 3 commits new 5bb020a66c 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 751c3599d7 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new d0c649a0a3 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new d95dd2557f 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] new ecc89ea82a 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] new 84bb228b4a 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] new f7e5c8f600 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits new c5114bc423 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] new b84d47cf03 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] new 5b70d8982e 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] new 706dd1841b 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 443707ccee 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] new d979dafb0d 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] new f0272d78b2 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] new 40e47481e8 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] new bb24daaaba 172: onsuccess: #1687: 7: Success after gcc: 11 commits new f114867110 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] new 8db8c03c00 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] new 7c4a1de14b 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] new 3118aff35c 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] new d060dc5e01 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] new 1328bdfba2 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] new d3847b9def 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] new 959cfe0986 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] new 4ded9f10a6 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] new f09433a3f5 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits new ced17500a7 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] new 9bd5e54873 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] new 02340dfe33 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] new 8f46b28f34 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] new cb8d33f884 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] new cee9cae54a 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] new 96882c9c4e 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] new 96421f36e8 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 8a2b6cb5d9 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 3f55a6371c 192: onsuccess: #1848: 7: Success after linux: 213 commits new 723be450f9 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] new c37bf07822 194: force: #1853: 7: Success after gcc: 26 commits new d41f3fd066 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-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 (85bf2d8326) \ 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 1716 -> 1612 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 30868 -> 30500 bytes 05-build_abe-stage1/console.log.xz | Bin 91400 -> 90376 bytes 07-build_abe-linux/console.log.xz | Bin 8844 -> 8760 bytes 08-build_abe-glibc/console.log.xz | Bin 237872 -> 236108 bytes 09-build_abe-stage2/console.log.xz | Bin 224860 -> 220384 bytes 10-build_abe-gdb/console.log.xz | Bin 38376 -> 0 bytes 11-build_abe-qemu/console.log.xz | Bin 31364 -> 0 bytes 12-check_regression/console.log.xz | Bin 3072 -> 3788 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 17 +- 12-check_regression/mail-subject.txt | 2 +- 12-check_regression/results.regressions | 9 + 12-check_regression/trigger-bisect | 2 + 12-check_regression/trigger-notify | 0 13-update_baseline/console.log | 70 ++--- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/score/results-functional.json | 1 - git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 312 +++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 17 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 15 +- 30 files changed, 415 insertions(+), 75 deletions(-) delete mode 100644 10-build_abe-gdb/console.log.xz delete mode 100644 11-build_abe-qemu/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 delete mode 100644 dashboard/squad-vs-first/score/results-functional.json 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