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 d41f3fd066 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] discards c37bf07822 194: force: #1853: 7: Success after gcc: 26 commits discards 723be450f9 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] discards 3f55a6371c 192: onsuccess: #1848: 7: Success after linux: 213 commits discards 8a2b6cb5d9 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 96421f36e8 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 96882c9c4e 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] discards cee9cae54a 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] discards cb8d33f884 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] discards 8f46b28f34 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] discards 02340dfe33 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] discards 9bd5e54873 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] discards ced17500a7 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] discards f09433a3f5 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits discards 4ded9f10a6 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] discards 959cfe0986 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] discards d3847b9def 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] discards 1328bdfba2 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] discards d060dc5e01 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] discards 3118aff35c 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] discards 7c4a1de14b 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] discards 8db8c03c00 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] discards f114867110 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] discards bb24daaaba 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards 40e47481e8 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] discards f0272d78b2 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] discards d979dafb0d 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] discards 443707ccee 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] discards 706dd1841b 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits discards 5b70d8982e 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] discards b84d47cf03 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] discards c5114bc423 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] discards f7e5c8f600 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits discards 84bb228b4a 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] discards ecc89ea82a 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] discards d95dd2557f 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] discards d0c649a0a3 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] discards 751c3599d7 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits discards 5bb020a66c 157: onsuccess: #1672: 7: Success after gcc: 2 commits discards 9b92bb1848 156: onsuccess: #1671: 7: Success after gcc: 3 commits discards 8391576780 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] discards dbd6e0e59e 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] discards 3a55f73a21 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] discards 15fb2401a2 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] discards df1b45579e 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] discards 18e1db2e6f 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] discards 6b8f281c08 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] discards 496dd146c4 148: onsuccess: #1663: 7: Success after glibc: 2 commits discards 03c6ad700f 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] discards c2ffd65205 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] discards d9a787cc7b 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] discards 5cd7135089 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits discards 04e5a0c9f9 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] discards 4dd8182dda 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] discards d08d3d31ac 141: onsuccess: #1656: 7: Success after gcc: 7 commits discards 8aefe22ffb 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards ede5a4239c 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards fdc6f871bf 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 618d768cd5 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 0a9b6b2c7b 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 33dfef1c3f 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards a8083e80c0 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 9b40e94213 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 7e3659c2db 132: onsuccess: #1645: 7: Success after linux: 23 commits discards 5adc9e6b1a 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards c6f349a1b7 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards e5f9c0006e 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards 55c803329e 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 7d24372614 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards 255d5f9fb5 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 2036686e25 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 4a1d306a65 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 494e2b3b37 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards fc63dcfa89 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 2260c32749 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 9e62c4ea1b 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 2a77a4868f 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 665a30f379 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards e62ca6ded2 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards bc90f3f6a7 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 9192c75ba4 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 23c5b574f9 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 7944e5d4fa 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 41a43dbf47 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards c5b887a093 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 39ced6b935 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards a33208ad59 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards b2ca67beb9 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards 13e69dd028 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 7524524b6b 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards d672446229 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 5b2b406eef 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards d9570d5406 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 1df75c3685 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards 0e3ce92da7 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards ac002067c7 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 44978d2987 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 563a2e6ab3 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards c0e96aef36 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards aaf683a1ee 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards fb58d7638b 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 061d70a38c 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new a24e4da003 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 5f7d709358 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 8a54a5cde5 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 5eebb005c8 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 3a97ef4c36 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new 8a6559c50c 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 8c82dd99ca 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 4805b8a912 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 6c41028305 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 374554ac16 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new b1735755ee 106: onsuccess: #1617: 7: Success after gcc: 2 commits new 1e3ef25e7d 107: onsuccess: #1618: 7: Success after gcc: 2 commits new d90550b12b 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new e6722e5b60 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new bb665730e6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 9cfc7b1fd0 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new b3236611ca 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new 5867a7e229 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 14667e3a37 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 35af827aea 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 88d052fb67 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new 5f01c56cb8 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new fb5ec03cd3 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new b289421e86 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 4b4f5e977b 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 9e32067533 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new a246a434be 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 41e556a4e1 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new eb39a24fd0 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 082b5f446f 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new b7f64b908c 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new dfb6208db5 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new 9161ad8040 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 38ce97e05b 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 8d214b9c74 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new af4c785411 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 9e0923fb20 132: onsuccess: #1645: 7: Success after linux: 23 commits new 44f03966f3 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 3dfe433e2e 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new c56cf2746f 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 287f521f66 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 080414fbcf 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 83cbcb29fa 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 5fae420d7d 139: onsuccess: #1654: 1: Success after gcc: 11 commits new b19c2e6049 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 07a5daa1fb 141: onsuccess: #1656: 7: Success after gcc: 7 commits new 06a87af61b 142: onsuccess: #1657: 7: Success after binutils/gcc/linux/g [...] new e74262a521 143: onsuccess: #1658: 7: Success after binutils/gcc/linux/g [...] new 2de125b66c 144: onsuccess: #1659: 7: Success after binutils/gcc/gdb: 4 commits new 342f2ccd84 145: onsuccess: #1660: 7: Success after binutils/gcc/gdb: 10 [...] new 3accb3a201 146: onsuccess: #1661: 7: Success after binutils/gcc/linux/g [...] new d3f79da9c1 147: onsuccess: #1662: 7: Success after binutils/gcc/glibc/g [...] new 52e2bb46cb 148: onsuccess: #1663: 7: Success after glibc: 2 commits new 096780acc5 149: onsuccess: #1664: 7: Success after binutils/gcc/gdb: 32 [...] new 5d6f5b58bd 150: onsuccess: #1665: 7: Success after binutils/gcc/linux/g [...] new 143369cc25 151: onsuccess: #1666: 7: Success after binutils/gcc/linux/g [...] new aa2f5309c5 152: onsuccess: #1667: 7: Success after binutils/gcc/glibc/g [...] new 0c5ff29de7 153: onsuccess: #1668: 7: Success after binutils/gcc/gdb: 22 [...] new 08dd62c66b 154: onsuccess: #1669: 7: Success after binutils/gcc/linux/g [...] new 65e426c7c6 155: onsuccess: #1670: 7: Success after binutils/gcc/linux/g [...] new 6196c5337d 156: onsuccess: #1671: 7: Success after gcc: 3 commits new ad3f10ce96 157: onsuccess: #1672: 7: Success after gcc: 2 commits new 3a21763ca7 158: onsuccess: #1673: 7: Success after gcc/linux: 21 commits new 9f0db99aa1 159: onsuccess: #1674: 7: Success after binutils/gcc/glibc/g [...] new 5079fb0f93 160: onsuccess: #1675: 7: Success after binutils/gcc/gdb: 18 [...] new c3a0802928 161: onsuccess: #1676: 7: Success after binutils/gcc/linux/g [...] new 7ec9a4a14c 162: onsuccess: #1677: 7: Success after binutils/gcc/linux/g [...] new 3b08c13118 163: onsuccess: #1678: 7: Success after binutils/gcc/gdb: 5 commits new 0c4681c204 164: onsuccess: #1679: 7: Success after binutils/gcc/gdb: 18 [...] new 4d10c19a4a 165: onsuccess: #1680: 7: Success after binutils/gcc/linux/g [...] new 10088170ad 166: onsuccess: #1681: 7: Success after binutils/gcc/linux/g [...] new 0038f75b8d 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new d6e3306971 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: 34 [...] new 2a922bc5a5 169: onsuccess: #1684: 7: Success after binutils/gcc/linux/g [...] new bdd8c80399 170: onsuccess: #1685: 7: Success after binutils/gcc/linux/g [...] new d342c9f0d1 171: onsuccess: #1686: 7: Success after binutils/gcc/linux/g [...] new 62d893866c 172: onsuccess: #1687: 7: Success after gcc: 11 commits new 34b57a5a6b 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qemu [...] new de5ce5c021 174: onsuccess: #1689: 7: Success after binutils/gcc/linux/g [...] new ea2529677c 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: 17 [...] new ae00a1aaac 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc/g [...] new 6bfbf0e78a 177: onsuccess: #1692: 7: Success after binutils/gcc/linux/g [...] new ef7e527b1a 178: onsuccess: #1694: 7: Success after binutils/gcc/linux/g [...] new 65388c2450 179: onsuccess: #1696: 7: Success after binutils/gcc/linux/g [...] new e2d73b5260 180: onsuccess: #1724: 7: Success after binutils/gcc/linux/g [...] new cac3aa725f 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] new c0dfee6e12 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits new f6a4d72bc4 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] new eb01ea05a4 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] new f2b4007736 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] new 04bbbd9b6d 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] new 37dc3c2154 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] new ae543da45f 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] new fb32d787a4 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] new 82c2845682 190: onsuccess: #1834: 7: Success after binutils: 25 commits new f9394804ae 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 4ed0672e07 192: onsuccess: #1848: 7: Success after linux: 213 commits new 4a6cddaf44 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] new 02c0bbdbd6 194: force: #1853: 7: Success after gcc: 26 commits new 0c450100d5 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] new 59b2fca441 196: onsuccess: #1855: 4: Success after gcc: 30 commits
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 (d41f3fd066) \ 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 1612 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30500 -> 30364 bytes 05-build_abe-stage1/console.log.xz | Bin 90376 -> 90132 bytes 07-build_abe-linux/console.log.xz | Bin 8760 -> 8736 bytes 08-build_abe-glibc/console.log.xz | Bin 236108 -> 236564 bytes 09-build_abe-stage2/console.log.xz | Bin 220384 -> 202160 bytes 12-check_regression/console.log.xz | Bin 3788 -> 2940 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 26 ++- 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 | 72 ++++---- dashboard/dashboard-generate.sh | 2 +- 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 | 26 ++- mail/mail-subject.txt | 2 +- manifest.sh | 22 +-- results | 9 - 27 files changed, 75 insertions(+), 424 deletions(-) delete mode 100644 12-check_regression/results.regressions delete mode 100644 12-check_regression/trigger-bisect delete mode 100644 12-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh