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_check_gcc/master-arm in repository toolchain/ci/base-artifacts.

discards 6e01019417 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 874198af85 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 616028e5cf 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards a4a5a708bc 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards fdd4cb18ad 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 669554203e 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 756d0ee525 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 10dfc2d8cf 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 9a612caa9d 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 9c2dc5a22c 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 2c92c18364 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 78fb0aa2e8 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards de9aad1186 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 10638ef600 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 32c715c6b4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 32835372e2 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 3cacbb311e 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 339164b8aa 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 6c28f0b41c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards e7d3a46864 128: onsuccess: #1723: 1: Success after linux: 12 commits discards ec48df4b0c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 5592b86198 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards ed8d9c139c 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 39f03e09b1 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 97c7b954bf 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards e4a565b4b6 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards cd3984760d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards ac7d577305 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards d5bceed6b3 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 1d93f05c60 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 9661acff43 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 69bedf934e 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards a4d5662b2a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards b882bf8dfd 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards ed8bb9ecdd 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 95c76b2b10 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards e7fba326bf 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 3c1841be1b 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 829786e21f 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards d0ab181c7e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 3ce2a181d8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards b8b9830ddc 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 9ec49e605c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 6e38b16556 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 00a3d15faa 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 6a190a5c77 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards e7372ac4cf 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards bce34a74bf 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards fa39ebdc74 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 4357bc2c00 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 7bd818a9a1 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 11e749815b 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards ba8dc622d3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards cdbe3ca52c 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 98c92eeefe 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards d4a5d9b33e 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 7cb8d33dec 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 41424d79b5 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f424cb1249 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2af8bf8a20 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 89d4295089 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b3e2bdceba 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards ba8d7aaf69 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 5fad5a2d39 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards bd45238dcf 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 2ab5f7bfe0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards ac6ac3e0c8 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c869ca023d 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 2fa0f36625 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 5e7bab3c95 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e7d50687ec 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 15f279974e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 2f9e476809 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1c5bb0c3b8 74: onsuccess: 1: Successful build after linux: 44 commits discards 7222fb6191 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 84ca4c0489 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc6c91118a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 19cd1b5966 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 179e926b6b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 150a6b0a0e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bc0630a88b 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dcaa6d8185 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9a15510758 65: onsuccess: 1: Successful build after gcc: 4 commits discards ce88bf9163 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f0f37f1557 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3abdb8b078 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards e78e9c869f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 2eb13c4887 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 472e50c11f 59: onsuccess: 1: Successful build after glibc: 2 commits discards cfa78e3f0d 58: onsuccess: 1: Successful build after binutils: 2 commits discards 4504a5d491 57: onsuccess: 1: Successful build after gcc: 7 commits discards 2fba437416 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 45a8c35d78 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0531b34a39 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards edd36246de 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 62e3e38940 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards bd4737eab6 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2108ac35b2 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 50419f56f5 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 08bb27195c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 3010bda873 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1905d8a1d8 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 50f6842b3a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 532ead1b83 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3d705e2ace 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 067bc32d3e 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f44cafd70f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 07dfc6de28 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 24d22df4af 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new b1fc74e027 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9f45ac32a7 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 290222a313 57: onsuccess: 1: Successful build after gcc: 7 commits new 4d3f298697 58: onsuccess: 1: Successful build after binutils: 2 commits new 001db9eebe 59: onsuccess: 1: Successful build after glibc: 2 commits new 1c7abcd883 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new dd2800403a 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 2442c4c07e 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 6c13b1b4e2 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d485700f1c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 76a5a75a4c 65: onsuccess: 1: Successful build after gcc: 4 commits new 12bd1e73ba 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 51bc0138f7 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2f5277ef5e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a434b5d0fd 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 159d9116ca 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new f7b7b8aa4a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new ba5d4b4c63 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6a5c226248 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 135a659a82 74: onsuccess: 1: Successful build after linux: 44 commits new d9a1682456 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8f9aa06aa1 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 9f4ee516df 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 18c3fb3e77 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fbde6004a5 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 073cdc08b5 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 4706f77d49 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 0a9ab7c298 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 68b19f82ae 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new ef1946ed85 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 683deeeb01 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 0f7362f793 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new bbce0b12e8 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 992e7395f2 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new e6e666d838 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new adb175c715 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 205c43fefa 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 89aefb98e5 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 65c67a03f6 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new d8772de64b 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 2528a3bdf4 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 798b0e1ebb 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 2b108f5b5a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 8def3bed92 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new db09a44a81 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 43ff174a36 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new e799e8405e 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 22a52a5f61 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 1b8a06d1d7 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 3b13f519c2 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 343865baa9 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 7fa5573035 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 4fcbc07093 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 046ca4440a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 7eaaebb426 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 283b91cc85 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 3e25c39d5f 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 99100ad592 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new df06bac642 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 17e4d4a13f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new c19efbc729 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 800e64eb0a 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new f509b3e9f8 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new d0b597f2aa 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new d53ead43ee 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 3ac07afa97 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 1b5b409b8f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 298eef0430 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 1e5a1d8316 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 61ce0bf6ac 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 54b10c88ea 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 1783a9a610 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new cd0c215bc2 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 36cc0810e5 128: onsuccess: #1723: 1: Success after linux: 12 commits new c9dc40cc9c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 8017bd45a4 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new c97950aa67 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 02e0509ec6 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new e8dc81a960 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new e73c190057 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 37ee5bcfbc 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 7a38ef4a23 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 6125e5ad08 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 203820eb85 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new bf28cf4e91 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 2d06afc5b7 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 7aaeba662c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 56214ad86a 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 87696960dd 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 59e19a4eda 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 4688e9cbe2 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new e3c16571fc 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 2d0f4342c1 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 5948b5117f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/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 (6e01019417) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]

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 1684 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29912 -> 30300 bytes 04-build_abe-stage1/console.log.xz | Bin 90360 -> 90676 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8432 -> 8468 bytes 07-build_abe-glibc/console.log.xz | Bin 233124 -> 233904 bytes 08-build_abe-stage2/console.log.xz | Bin 223648 -> 223088 bytes 09-build_abe-gdb/console.log.xz | Bin 37240 -> 37588 bytes 10-build_abe-qemu/console.log.xz | Bin 31424 -> 31360 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2428 -> 2764 bytes 13-check_regression/console.log.xz | Bin 6528 -> 5912 bytes 13-check_regression/mail-body.txt | 47 - 13-check_regression/results.compare | 32 +- 13-check_regression/results.compare2 | 100 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 49 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- sumfiles/g++.log.xz | Bin 2671680 -> 2681660 bytes sumfiles/g++.sum | 108 +- sumfiles/gcc.log.xz | Bin 2236828 -> 2193204 bytes sumfiles/gcc.sum | 2256 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 889400 -> 882492 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201272 -> 201232 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 433956 -> 423400 bytes sumfiles/libstdc++.sum | 16 +- 40 files changed, 1311 insertions(+), 1483 deletions(-)