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 2c249afb12 305: force: #2006: 7: Success after gdb: 2 commits discards 7a1ed76f97 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 025b875193 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards afd29a301f 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards bf8ab4d38d 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 03e0b91a36 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards 5d2696796c 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards 03e529eda9 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards 1060259996 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards 5b4a31105d 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards 1739c6d5ff 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards f440e421c8 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards d00b62143b 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards 39c23ec210 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards def3398ba3 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards 9d95e134d8 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards 03d95bc575 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards cc90549712 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards f58755b1fe 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards 972541fa25 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 183c051e44 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards e2f2ab9ec2 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards a4b2b4dc72 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards 9435a90a8e 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards ac00246a4c 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards 305943ef5a 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards f7395c29bc 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards 7035b197d7 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards 6bb10a70f5 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards 9e94f7ac3d 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 6612709a50 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards 0e50cffb9d 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards 35ac8272a4 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards d7cc133527 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards 75c6c6ee2b 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards 7de79fafce 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards 7c96e30f7f 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards 17d6aab6c0 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards 29819eec60 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards 63927c8095 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards d397d6825b 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards 8e7670f590 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards b54577531c 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards 6c46427c27 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards 9386ad4f5b 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards d826563f49 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards cf048a7176 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards abdb312075 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards 0e19185898 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards 496d2c5c6b 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 48bf688e80 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards 58fc8c1618 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards dc5fce6954 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards bd9db73819 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards 1f88275f8c 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 016194d900 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards 6112190c66 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards 0b2d583084 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards 2a09f7b682 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 2cededd310 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards f20c6b0300 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards 6d0ddafeba 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards 96aff88f3d 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards ae05e6f69a 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards 9325439d56 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards 37add7e626 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards bf5c7988a8 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards 09bbd6837e 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards 6435de4261 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards ce83375626 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 932789154d 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards fd0e69fb3b 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards 1b94b4285c 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards 26a7d43c1e 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards 6507f712ea 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards b488369c4f 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards 1b18361c98 229: force: #1926: 7: Success after gcc: 7 commits discards 753f268745 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] discards e18dc31879 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards c6b545c543 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] discards 1a46eea660 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] discards 578819e340 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] discards 89ef3a66a1 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] discards f5f559b375 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] discards d78f06f3ce 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] discards e29b9494ec 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] discards 15f61da5b9 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits discards ac5ef50012 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] discards c380b71a61 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] discards 90ebdb2e9f 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards e9b511ed94 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] discards 6d81f7937e 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] discards 52ba6b84d3 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards a9e3852c32 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] discards 408be0718e 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] discards 17eb6ce577 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards d3a43c8efc 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] discards 4ffd4429b4 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 6d15012695 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards 6f4d639c7b 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards bac98c05ce 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 46ca07c197 205: onsuccess: #1859: 7: Success after gcc: 3 commits new d52544cbd3 206: onsuccess: #1860: 7: Success after gcc: 2 commits new b76cd0bd13 207: onsuccess: #1862: 7: Success after binutils: 4 commits new 79b5344c3e 208: onsuccess: #1865: 7: Success after linux: 12 commits new 45ad8ef6ef 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] new 16ce1134c4 210: onsuccess: #1868: 7: Success after binutils: 7 commits new e8156329e3 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] new 92213d524a 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] new 9c929e9e5c 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 56798982a0 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] new 78553024f3 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] new 1b24f84f96 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new 246fd0c542 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] new 07fc612170 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] new 20e1be10e2 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits new 05647aaf1c 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] new fdccbb462e 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] new 57e9e3b0b4 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] new ec7f17e96c 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] new 50a379e0a8 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] new a9f0e97f22 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] new dc8133fb61 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new 903a5ac748 227: onsuccess: #1906: 7: Success after binutils: 9 commits new baf66f15b6 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new 5495ecf8c0 229: force: #1926: 7: Success after gcc: 7 commits new 2cbc6b1804 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new 6c30f5b173 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 5dbdbc681c 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new 2792cd8540 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new d3957c0827 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new 249f62c553 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new f437823544 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 2918fb58f6 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new b9e42a0592 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new 26ccad8ef4 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new 86890d7cb6 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new f3cd146c6b 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new 7a58a1250d 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new 4c5cc02c5c 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new 8208d73cf0 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new 9e84d8cab9 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new c4ae240a4a 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 6e2676e4ff 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new 2112e562f3 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new 28397c6f61 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new 301efc8b9d 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 25e02ef6e7 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new 9e83da319c 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new dced5517cb 253: onsuccess: #1950: 7: Success after glibc: 2 commits new f95f53bdf6 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new b406447d7a 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 58d5f9bb99 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new 65855d3647 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new 11099b9d84 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new 00f38687c0 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new 868c5c5c6c 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new 99de18cd59 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new 65a06279b6 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new 6cddbaa829 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new 162e04eacb 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new 7757525844 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new 03e14760ec 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new da07fff7d4 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new e99c979d12 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new d86573e9bd 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new b650936c3e 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new 40947ab95d 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new b8a17f47dd 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new 43a7e613a3 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new 994dd322fb 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 345ef9784f 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new f28911ad8a 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new 2a0465bb7d 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new cc107d4c87 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new 2af207c855 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new 1f16746fbb 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new 51c2c02f19 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new 13afff1a10 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new 7db7af6925 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new f3bbc5f9bd 284: onsuccess: #1981: 7: Success after gcc: 2 commits new 6f5384acef 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new 9470238c22 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new 5cb14f24ee 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new 69c8de141b 288: onsuccess: #1985: 7: Success after gcc: 17 commits new da0112d327 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new 1c84e6dff9 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new 999c6c8d29 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new 66884c7ce3 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new 93dccd0661 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new cbf47fdb66 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 66f05ccc98 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new b723852010 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new aa62c14fc6 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new f81974ee92 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new a9472f21da 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new dded69c6b3 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new 2377794ad3 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new c49e986f65 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 25795ce68d 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 38049d7a0b 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 0da47ca43e 305: force: #2006: 7: Success after gdb: 2 commits new 4c1be4c99c 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-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 (2c249afb12) \ 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 1744 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 32092 -> 32168 bytes 05-build_abe-stage1/console.log.xz | Bin 74012 -> 73892 bytes 07-build_abe-linux/console.log.xz | Bin 8520 -> 8528 bytes 08-build_abe-glibc/console.log.xz | Bin 245432 -> 245148 bytes 09-build_abe-stage2/console.log.xz | Bin 205564 -> 204928 bytes 10-build_abe-gdb/console.log.xz | Bin 39572 -> 36604 bytes 11-build_abe-qemu/console.log.xz | Bin 31504 -> 0 bytes 12-check_regression/console.log.xz | Bin 2952 -> 3724 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 10 +- 12-check_regression/mail-subject.txt | 2 +- 12-check_regression/results.regressions | 4 + 12-check_regression/trigger-bisect | 2 + 12-check_regression/trigger-notify | 0 13-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/score/results-functional.json | 1 - git/gdb_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 1072 ++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 10 +- mail/mail-subject.txt | 2 +- manifest.sh | 23 +- results | 8 +- 30 files changed, 1141 insertions(+), 52 deletions(-) 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