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-aarch64 in repository toolchain/ci/base-artifacts.
discards 6277c1688b3 229: force: #1926: 7: Success after gcc: 7 commits discards 83f652dafd0 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint- [...] discards cb41740e34b 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards 1aa0085c955 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 3 [...] discards a109a450253 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/ [...] discards d29e4c19285 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/ [...] discards 803c1ebeafd 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-4 [...] discards 4a75d217c16 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/ [...] discards 4492a9de235 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 1 [...] discards a715aef017b 220: onsuccess: #1898: 7: Success after binutils/linux/glib [...] discards 20ee48c555f 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 [...] discards 5e52d3434b7 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/ [...] discards 1e65caa3fa0 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 1 [...] discards 1522892c50e 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards f342b7dc157 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/ [...] discards 906d11e8afc 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/ [...] discards 655450b6bfe 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards ef6598b00e5 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/ [...] discards 85f498db03b 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/ [...] discards 5dd99eef7a6 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards 0e6e7e47b3f 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qe [...] discards cae54e57af7 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 4e84f8ad99f 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards f6025502fb3 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards 59bf38026b6 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards 054f6b9e0ed 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/ [...] discards f6475d43305 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 [...] discards 5cdc0cf5841 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards 9b31361e188 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/ [...] discards 4492d8d808b 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards 2d70c0440d6 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 1 [...] discards 1bec2620a03 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards 5f669570c03 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/ [...] discards 19403735f25 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] discards 7e73d564c83 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] discards 80418a1a8e9 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] discards d9b4150d732 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] discards 3da6ebcff76 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] discards 111a3d3c6d3 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] discards 2c01118d686 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 4727e2327e9 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] discards d2b2b734998 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] discards 95ce662b8e3 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] discards c494c603037 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] discards 9c4c8aef38c 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards 8a40591b7d7 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] discards f59c57c6820 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] discards df146309552 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] discards 4f998b83fcc 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] discards 37c205b5c3c 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards fa873d33bde 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] discards 8a2fb8993d4 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] discards 3bf363eeb01 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] discards 06aae8687b3 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] discards 44242edb5b9 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] discards cdc14d5fd3f 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] discards 89fc2f54b4f 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] discards b0deb98efcb 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] discards 889c96ff942 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] discards d229adbd747 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] discards ee6a013798c 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] discards 4db40f09db3 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] discards b63794816f6 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] discards ab4ee37fe3d 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 60b2ba24495 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] discards 0e2faa4d7da 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] discards b6f25d04f7c 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] discards 80dca91bf45 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] discards 8737e05a5f1 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] discards bda29aae84a 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] discards 2d1df2f73b9 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards a839c634cd4 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] discards f58ef8bae6e 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 89ac36e664d 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards d15f6158296 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] discards 80f56fc0517 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards ffec3531d83 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] discards 64c0bb0aa5e 152: force: #1605: 7: Success after gcc: 9 commits discards 275ab61dab9 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] discards 8d6cbb1baed 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] discards 940b8d76a90 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] discards 0a4de650bf7 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] discards da522682986 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] discards 535b595a297 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] discards 4c11ebecea6 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] discards 8e695d884bb 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 13db7fb31c3 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] discards 07dd1236e5a 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] discards f7959cd9fa5 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] discards 304d3e1a9d4 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] discards 61989b8468f 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] discards 63938b540aa 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] discards 8cbc062d2c3 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards c78aca60760 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] discards 110ca30fe3b 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] discards fd908045fb4 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] discards 96f2fc26703 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] discards bb2611e4eb3 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] discards 62ac5cec52b 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] discards c93cecf0b11 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 915a48ff9a1 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] new a60e9230628 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-2 [...] new c9a3628d0b0 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new b4f661a0f2b 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/ [...] new 81c23455cab 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 1 [...] new 08e721eea3f 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 2 [...] new f88463f57ed 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/ [...] new c6a3a5a584b 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/ [...] new 70dfffc89fa 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 1 [...] new 56525638bdd 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 474bcd98e38 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/ [...] new b4dc3a2fd54 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/ [...] new 421703b1b9c 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 [...] new e8b7d36388a 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 [...] new a23ad9db0d1 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/ [...] new 2e884b08d87 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/ [...] new 96a565540b9 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 6a6e153a801 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 3 [...] new 67951ac4bfe 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/ [...] new fe39931933d 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/ [...] new 9b0d4f48b01 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/ [...] new ce95634d092 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 2 [...] new ebc8526a60c 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/ [...] new 6c30f149605 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint- [...] new f1ebce4afdb 152: force: #1605: 7: Success after gcc: 9 commits new 38dab25050a 153: force: #1606: 1: Failure after basepoints/gcc-13-3004- [...] new 9a7abeaa889 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 5c0a504e3f0 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb [...] new c7b292e8a9f 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 5523ff62241 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new 7e0ee19c5e7 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc/ [...] new f3ab17443de 159: onsuccess: #1612: 7: Success after gcc: 4 commits new f8fa48c2e73 160: onsuccess: #1613: 7: Success after binutils/gcc/linux/ [...] new 2df7d5e7df3 161: onsuccess: #1614: 7: Success after binutils/gcc/linux/ [...] new 522a83697d2 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: 5 [...] new 8b4d8a5bbc3 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: 1 [...] new 64f9ec71709 164: onsuccess: #1617: 7: Success after binutils/gcc/linux/ [...] new da1ec358636 165: onsuccess: #1618: 7: Success after binutils/gcc/linux/ [...] new 53e99660d95 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 11ef98b288e 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 2 [...] new f416dd323e3 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/ [...] new 160266cb987 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/ [...] new 7f0673c68b9 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/ [...] new 4aa75a10f01 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 1 [...] new db80d3a3a56 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qem [...] new 6c080aae3dc 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/ [...] new 46e053d34cc 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 1 [...] new 5c39173288e 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/ [...] new a5c90477702 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/ [...] new 6833e3f01bf 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/ [...] new ab63d51b7a3 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/ [...] new bf32754c8b7 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/ [...] new 82f82981570 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new b2b824c2c19 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/ [...] new fdb91070b0b 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/ [...] new a73937c56df 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/ [...] new d30be12cd22 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/ [...] new ee6f4c2bc93 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new 07828d01f93 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/ [...] new a7298bc242f 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/ [...] new 2c14416e93f 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/ [...] new 0e13c010e6b 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 3 [...] new 2db08fcb1c5 190: onsuccess: #1774: 7: Success after binutils: 10 commits new 55088f68e85 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/ [...] new cb8efab2d42 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/ [...] new 7e2834ee9f7 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/ [...] new eff57dd18de 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 1 [...] new 333c61126bc 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 1 [...] new b3275337dc6 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 4 [...] new ad1c3d1e829 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/ [...] new 61ec29061be 198: onsuccess: #1852: 7: Success after gcc: 5 commits new fd5a32813e1 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 1 [...] new 0ed2556ac4d 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new d0b259a28c5 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/ [...] new b4231dc968d 202: onsuccess: #1856: 7: Success after gcc: 2 commits new de4620b4749 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 [...] new 43b8275faac 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/ [...] new 3ea70a41981 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 2cb108aeb7a 206: onsuccess: #1860: 7: Success after gcc: 2 commits new 23ee9da2067 207: onsuccess: #1862: 7: Success after binutils: 4 commits new 9a5be61d8d5 208: onsuccess: #1865: 7: Success after linux: 12 commits new aff43e8777f 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qe [...] new f8a046f73fa 210: onsuccess: #1868: 7: Success after binutils: 7 commits new b933b570a1e 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/ [...] new 0dff7ea0184 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/ [...] new 1b49b3c98a5 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 32f9ef3c398 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/ [...] new 5bb3a7662c1 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/ [...] new 46f365fe726 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new 1e41db815b0 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 1 [...] new 5346bf7c542 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/ [...] new 69fac4a4f25 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 [...] new d8bba93effd 220: onsuccess: #1898: 7: Success after binutils/linux/glib [...] new c65379869a6 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 1 [...] new 0413fb66824 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/ [...] new 4329a2913e3 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-4 [...] new c96ef1fb8c6 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/ [...] new ddd3b474fb1 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/ [...] new 2e563618a0e 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 3 [...] new 246b53ffcfa 227: onsuccess: #1906: 7: Success after binutils: 9 commits new 0b3a28f41d2 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint- [...] new 60aa56719fc 229: force: #1926: 7: Success after gcc: 7 commits new af6e06b73dc 230: force: #1927: 3: Failure after basepoints/gcc-13-4618- [...]
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 (6277c1688b3) \ 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 1824 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2784 bytes 04-build_abe-binutils/console.log.xz | Bin 32188 -> 32388 bytes 05-build_abe-stage1/console.log.xz | Bin 74172 -> 74520 bytes 07-build_abe-linux/console.log.xz | Bin 8592 -> 8508 bytes 08-build_abe-glibc/console.log.xz | Bin 245488 -> 168468 bytes 09-build_abe-stage2/console.log.xz | Bin 208200 -> 0 bytes 10-build_abe-gdb/console.log.xz | Bin 39492 -> 0 bytes 11-build_abe-qemu/console.log.xz | Bin 31088 -> 0 bytes 12-check_regression/console.log.xz | Bin 3224 -> 3828 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 15 +- 12-check_regression/mail-subject.txt | 2 +- 12-check_regression/results.regressions | 5 + 12-check_regression/trigger-bisect | 2 + 12-check_regression/trigger-notify | 0 13-update_baseline/console.log | 64 ++--- 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 | 314 +++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 +- mail/mail-subject.txt | 2 +- manifest.sh | 23 +- results | 13 +- 30 files changed, 395 insertions(+), 78 deletions(-) delete mode 100644 09-build_abe-stage2/console.log.xz 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