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 bf06d274ac 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards 06ff27e561 321: force: #2055: 7: Success after gdb: 2 commits discards 69f0de5567 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards 772de53d84 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards 19abd7c1f1 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards 1f8d35ab7b 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards daea131442 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 19d6ac18b9 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards e75bef0fc2 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards f26142980c 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards 08f82a3708 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards 0182143cc9 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards bc8796f8f9 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards 8515cca3c0 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 88f370be36 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 82852e944e 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards 95ff9efb00 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] discards 075e35c8ae 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] discards 46ff223f2a 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits discards 57173649e4 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards 027a281bca 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards 99d2ed7a51 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards 486b135e4e 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards 85574d00da 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards 3d713b1fb9 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards d407564706 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] discards 5927aea0ae 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits discards 196aa0012e 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] discards 882817d6d6 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits discards f6c746bfc6 293: onsuccess: #2022: 7: Success after gcc: 2 commits discards 109e12f4de 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] discards 48ea2c408f 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits discards 029fa747dd 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits discards 36d4941bf6 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] discards 195fb66705 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits discards 7242f14b89 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits discards 552b181b99 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] discards 250dcd68d3 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] discards 346d344c58 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] discards 3c84a9ec78 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 1279c98ed0 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] discards 5c154d325c 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] discards f3460395bb 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 823446afe9 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] discards ee66f978d8 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] discards eeb5fb4c86 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] discards 463be0c2f5 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] discards e2105d123f 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits discards 66a7fd5dcd 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] discards ca0ba380d5 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] discards ab5589064d 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] discards ce637f9810 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] discards ad1c650d81 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] discards 2bfc3bed23 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] discards 4f0c49d2f1 268: onsuccess: #1997: 7: Success after glibc: 2 commits discards 4d21679a37 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] discards 9389d94c9c 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] discards 88df039cd6 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits discards 91fe3fa82c 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits discards 4562a69f9d 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] discards 4ac60b0a6c 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits discards e0bd137d78 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] discards a31cdc676f 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] discards 6719f211e1 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] discards a26776c312 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] discards e7033798fb 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 832f3ca477 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] discards 49981cd3e8 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] discards c1f93f5076 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] discards 23f1a6a170 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] discards 2e0b36bd37 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] discards 14493a565e 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] discards bde9260853 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] discards 8133586d11 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] discards 606df20193 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] discards 4a939d8e12 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] discards 6d507bcd20 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] discards 686e5f959a 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] discards 0648458d87 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards fedaaaa6fb 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] discards 3f6b83f40e 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc/g [...] discards 3ae5e89363 241: onsuccess: #1970: 7: Success after binutils/gcc/linux/g [...] discards 7575898383 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits discards 73521e9650 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: 3 commits discards cfc9591f53 238: onsuccess: #1967: 7: Success after binutils/gcc/linux/g [...] discards 4e4bd4f594 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits discards c738ebd7c1 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 15 [...] discards c545e2be84 235: onsuccess: #1964: 7: Success after binutils/linux/glibc [...] discards ec23be609c 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 commits discards f876bce272 233: onsuccess: #1962: 7: Success after gcc: 6 commits discards 1aa2f3e68c 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/g [...] discards d219330b92 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/g [...] discards e4841bbcfc 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/g [...] discards 110e33f5c7 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/g [...] discards 0daa72d224 228: onsuccess: #1956: 7: Success after gcc: 5 commits discards e13ab850f3 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits discards 0795ab299f 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/g [...] discards e7363d34be 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards d90b280eed 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qem [...] discards 6b94017e12 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] discards 97a581dcbd 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-44 [...] new 1b80905215 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-44 [...] new c1afb912d3 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] new 6ce6982c8e 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qem [...] new 4cf3d80424 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new 59933ed3e0 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/g [...] new b349d2ca6b 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits new f416d32a12 228: onsuccess: #1956: 7: Success after gcc: 5 commits new 029939f282 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/g [...] new e5f2258b3b 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/g [...] new baf25b414d 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/g [...] new 287ee425ba 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/g [...] new 50decbf42c 233: onsuccess: #1962: 7: Success after gcc: 6 commits new 3e76f71205 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 commits new 94f514f1a9 235: onsuccess: #1964: 7: Success after binutils/linux/glibc [...] new 3426d9c772 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 15 [...] new cf1fb97e0b 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits new 6d12db86d1 238: onsuccess: #1967: 7: Success after binutils/gcc/linux/g [...] new afa18edeac 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: 3 commits new 65a712ccc0 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits new edb453da4b 241: onsuccess: #1970: 7: Success after binutils/gcc/linux/g [...] new 01b85fda00 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc/g [...] new 5f8e771d28 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] new a0590a4ce5 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new 8aa317eecc 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] new b320d54094 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] new 10d0f74312 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] new de7106516a 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] new e47b4b038f 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] new 990adb519d 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] new 2417d3c298 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] new 7563536aee 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] new c6ef4538ac 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] new a4564d9820 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] new 80e87cd278 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] new 6c816197f3 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] new b0d26ea0be 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new bcdedcfd75 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] new 10e9a1e727 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] new 6f7081b8ff 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] new c9c72ce00d 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] new 30d9c6dc91 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new 319733ed63 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] new 58c6b23b27 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits new 0fc55c52d1 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits new 30a9b4c4d4 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] new 2398c29bce 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] new c2955552ba 268: onsuccess: #1997: 7: Success after glibc: 2 commits new 570a7aaccb 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new 2cde104652 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] new 4a0f3195a5 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] new bd71f86860 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] new abbcbcb16d 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] new 60e022c541 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] new 3aa62bb14b 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits new ae4e6e453f 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] new e1df5d7710 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] new 711b19012a 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] new 95922e1e61 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] new 924131c3a0 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 39608816fb 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] new d2828b067b 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] new afaa27b6d5 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new c94dae7e00 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] new 0291da905d 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] new 750d21b1ca 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] new 04b603e75c 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits new e6e276a605 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits new 0d2c6a5513 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] new 872fcb83fb 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits new 74950091d9 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits new dfb2e11f5d 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new c5ebf95fc3 293: onsuccess: #2022: 7: Success after gcc: 2 commits new c4516ebeb2 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits new 973c9d6718 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] new d4021a174a 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits new 9ec1d18d9f 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new 01da2d05c3 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new ce45191f48 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new 6401f33d84 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new 00139b551e 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new 1cecf9d188 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new 1e0c870d19 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new a126a05510 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits new ebbccc0847 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] new 5b2269e7b0 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new 036798107d 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new bfde7df79e 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 1f6e540931 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new ab641c5a6c 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new 81e70db7d3 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new 550a085060 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new 1603f49dc1 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new 76545bdfc7 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new 658f7954a1 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new f710ba404c 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new b1db229ed1 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new 820be487b1 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new 9c16b9de95 319: onsuccess: #2049: 7: Success after binutils: 4 commits new b04e682c0f 320: onsuccess: #2050: 7: Success after gcc: 4 commits new 41a35bcdf7 321: force: #2055: 7: Success after gdb: 2 commits new 33428ccf57 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new 90bfadb7b1 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...]
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 (bf06d274ac) \ 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 1652 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 04-build_abe-binutils/console.log.xz | Bin 31996 -> 31780 bytes 05-build_abe-stage1/console.log.xz | Bin 92304 -> 92408 bytes 07-build_abe-linux/console.log.xz | Bin 8548 -> 8544 bytes 08-build_abe-glibc/console.log.xz | Bin 236768 -> 236388 bytes 09-build_abe-stage2/console.log.xz | Bin 229236 -> 228512 bytes 10-build_abe-gdb/console.log.xz | Bin 36464 -> 35788 bytes 12-check_regression/console.log.xz | Bin 3724 -> 2668 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 14 +- 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 | 66 +- dashboard/dashboard-generate.sh | 2 +- 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 | 14 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- results | 4 - 28 files changed, 62 insertions(+), 1157 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