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 5948b5117f 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 2d0f4342c1 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards e3c16571fc 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards 4688e9cbe2 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 59e19a4eda 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 87696960dd 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 56214ad86a 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 7aaeba662c 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 2d06afc5b7 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards bf28cf4e91 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 203820eb85 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 6125e5ad08 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 7a38ef4a23 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 37ee5bcfbc 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards e73c190057 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards e8dc81a960 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 02e0509ec6 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards c97950aa67 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 8017bd45a4 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards c9dc40cc9c 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 36cc0810e5 128: onsuccess: #1723: 1: Success after linux: 12 commits discards cd0c215bc2 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 1783a9a610 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 54b10c88ea 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 61ce0bf6ac 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 1e5a1d8316 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 298eef0430 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 1b5b409b8f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 3ac07afa97 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards d53ead43ee 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards d0b597f2aa 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards f509b3e9f8 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 800e64eb0a 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards c19efbc729 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 17e4d4a13f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards df06bac642 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 99100ad592 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 3e25c39d5f 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 283b91cc85 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 7eaaebb426 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 046ca4440a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 4fcbc07093 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 7fa5573035 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 343865baa9 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 3b13f519c2 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 1b8a06d1d7 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 22a52a5f61 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards e799e8405e 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 43ff174a36 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards db09a44a81 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 8def3bed92 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 2b108f5b5a 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 798b0e1ebb 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 2528a3bdf4 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards d8772de64b 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 65c67a03f6 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 89aefb98e5 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 205c43fefa 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards adb175c715 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e6e666d838 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 992e7395f2 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards bbce0b12e8 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 0f7362f793 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 683deeeb01 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards ef1946ed85 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 68b19f82ae 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 0a9ab7c298 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 4706f77d49 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 073cdc08b5 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards fbde6004a5 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 18c3fb3e77 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9f4ee516df 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8f9aa06aa1 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards d9a1682456 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 135a659a82 74: onsuccess: 1: Successful build after linux: 44 commits discards 6a5c226248 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards ba5d4b4c63 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f7b7b8aa4a 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 159d9116ca 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards a434b5d0fd 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 2f5277ef5e 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 51bc0138f7 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 12bd1e73ba 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 76a5a75a4c 65: onsuccess: 1: Successful build after gcc: 4 commits discards d485700f1c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6c13b1b4e2 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2442c4c07e 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards dd2800403a 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 1c7abcd883 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 001db9eebe 59: onsuccess: 1: Successful build after glibc: 2 commits discards 4d3f298697 58: onsuccess: 1: Successful build after binutils: 2 commits discards 290222a313 57: onsuccess: 1: Successful build after gcc: 7 commits discards 9f45ac32a7 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b1fc74e027 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 24d22df4af 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 07dfc6de28 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards f44cafd70f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 067bc32d3e 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3d705e2ace 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 532ead1b83 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 50f6842b3a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new da15d0032f 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 21dda0fc6f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b627aaa175 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b33ab3a079 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 384a44745f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new ca75dc5008 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 043c2aafea 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new bb994f7db3 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 839729bad9 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fd98804f7a 57: onsuccess: 1: Successful build after gcc: 7 commits new 17246d152c 58: onsuccess: 1: Successful build after binutils: 2 commits new 01d5b85d3a 59: onsuccess: 1: Successful build after glibc: 2 commits new 3fbb992695 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 925de18f72 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e5f9c9136d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new b60cbd9823 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6d5f2c5bd4 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7c379500cd 65: onsuccess: 1: Successful build after gcc: 4 commits new 0d0ea56fa2 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1effdfe09e 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bda6c7d34c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6f516485d0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new ee34af6070 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 558bf1f7ac 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 84f7d183c1 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e7be8be677 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 05ab332e63 74: onsuccess: 1: Successful build after linux: 44 commits new e005d35fab 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0c3ad31c28 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 26e10ff634 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fff0b9ac74 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b465e2b288 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new a794195b4c 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new e785018eb7 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new f2cc2b45d3 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 867899a3e1 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 78943fc972 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 71dbee2fc1 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 33a47a017c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 2d6e809b4c 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new cf163926a9 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new a598665c09 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a87a196cb6 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 10de729902 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new c25b899e02 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 37a3fab4c4 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 05f7a6540c 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 444f3b2cfb 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 8e83b96aa2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new f81b0af170 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 3ded6c973a 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new d344d64a8d 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 61ad149cb8 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 54012e09d7 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 246335503e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new aa1359c8b7 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new d478bc10d7 104: onsuccess: #1697: 1: Success after gcc: 4 commits new bcaafceae8 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 9f18136107 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 8091b72ed2 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 62d009622b 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 3f5589016e 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 40d864c120 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 1744358d53 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 9dc1dda699 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new d642121417 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 507908ffa8 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new a4099feeae 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new beaff14e73 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new b3b06a00d4 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 18bf013f30 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 7652f7a4d9 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new 80033c4968 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 5adf637d7d 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 2232942f49 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new f9dd369e53 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new feda6cced5 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 62c140a10a 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 66260b16de 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new e60a4cfebf 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new c4f369d8d0 128: onsuccess: #1723: 1: Success after linux: 12 commits new dc53777d86 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new c604a8d9a4 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new b9f3d97bd4 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 85d0a03403 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new e5f1682e4d 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 957ba58bf8 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 2e1c24e86b 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 289cb3277c 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 232b85ceba 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 4efd64c9c7 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 3e15bd5fb6 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new da000130be 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 59e16aafb8 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new bfd16e44d9 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new f0ade27006 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 46f65a82ce 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 04170bf518 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 62d6233a8d 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new 4e176eaf40 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 52df9a66f1 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new 570ce02f4b 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...]

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 (5948b5117f) \ 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 1740 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30300 -> 29912 bytes 04-build_abe-stage1/console.log.xz | Bin 90676 -> 91120 bytes 06-build_abe-linux/console.log.xz | Bin 8468 -> 8464 bytes 07-build_abe-glibc/console.log.xz | Bin 233904 -> 233632 bytes 08-build_abe-stage2/console.log.xz | Bin 223088 -> 223696 bytes 09-build_abe-gdb/console.log.xz | Bin 37588 -> 37252 bytes 10-build_abe-qemu/console.log.xz | Bin 31360 -> 31988 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3848 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2764 -> 3156 bytes 13-check_regression/console.log.xz | Bin 5912 -> 6496 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 84 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 26 + sumfiles/g++.log.xz | Bin 2681660 -> 2694152 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 2193204 -> 2209208 bytes sumfiles/gcc.sum | 1968 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 882492 -> 880904 bytes sumfiles/gfortran.sum | 12 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201232 -> 201412 bytes sumfiles/libgomp.sum | 45 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423400 -> 425084 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 1293 insertions(+), 1096 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions