This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.

discards 5e0321de6e66 133: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] discards c7c9af9a1790 132: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] discards 24e9ea2f5f5a 131: onsuccess: #880: 1: Success after binutils/gcc/linux/ [...] discards 9d75104dd4a4 130: onsuccess: #879: 1: Success after binutils/gcc/linux/ [...] discards f4e739c2c37e 129: onsuccess: #878: 1: Success after linux: 3008 commits discards f9a0e4bbd76f 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 7d6eb0e7da34 127: onsuccess: #874: 1: Success after linux: 219 commits discards f6e1a362aed2 126: onsuccess: #873: 1: Success after glibc: 2 commits discards aee078522342 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 7df7160e8544 124: onsuccess: #869: 1: Success after binutils/gcc/linux/ [...] discards b1b2738c77de 123: onsuccess: #868: 1: Success after binutils/gcc/linux/ [...] discards 2c115de04fe5 122: onsuccess: #867: 1: Success after binutils/gcc/linux/ [...] discards 1259d5fb9a8a 121: onsuccess: #866: 1: Success after binutils/gcc/linux/ [...] discards 05aee1a0146a 120: onsuccess: #865: 1: Success after binutils/gcc/linux/ [...] discards c999135a3dd4 119: onsuccess: #864: 1: Success after binutils/gcc/linux/ [...] discards f79c3d121b38 118: onsuccess: #863: 1: Success after linux: 12 commits discards c47602f86a58 117: onsuccess: #861: 1: Success after binutils: 18 commits discards b869f9191c5f 116: onsuccess: #859: 1: Success after binutils/gcc/linux/ [...] discards 7babce8f62e2 115: onsuccess: #858: 1: Success after binutils/gcc/linux/ [...] discards f201ae473f57 114: onsuccess: #857: 1: Success after binutils/gcc/linux/ [...] discards fdf049936e5c 113: onsuccess: #856: 1: Success after binutils/gcc/linux/ [...] discards 789bc7b4a658 112: onsuccess: #855: 1: Success after binutils/gcc/linux/ [...] discards d442b041a0be 111: onsuccess: #854: 1: Success after binutils/gcc/linux/ [...] discards 0cce8bbb8992 110: onsuccess: #853: 1: Success after binutils/gcc/linux/ [...] discards bd9c2d3dca1a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/ [...] discards 1c6a30a2dd67 108: onsuccess: #850: 1: Success after gcc: 2 commits discards a9b98a70ebc5 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 54ecb52bc97f 106: onsuccess: #847: 1: Success after binutils/gcc/linux/ [...] discards b287ac99fb5a 105: onsuccess: #846: 1: Success after binutils/gcc/linux/ [...] discards f12002ffb47f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 6 [...] discards 0136f8e9a48e 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 5 [...] discards 923450ae222e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/ [...] discards 0f829e5d1e9e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/ [...] discards 44ba5237a355 100: onsuccess: #841: 1: Success after binutils/gcc/linux/ [...] discards 9d99aea9449d 99: onsuccess: #840: 1: Success after binutils/gcc/linux/g [...] discards 81ebcf37e46e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] discards 2ba0e9ef64b6 97: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] discards 89a0617acc2b 96: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] discards 52573bb364ba 95: onsuccess: #835: 1: Success after binutils: 3 commits discards f24d7e217214 94: onsuccess: #832: 1: Success after binutils: 5 commits discards abb6ca043624 93: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] discards 8855e87bd871 92: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] discards 84036d7417ff 91: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] discards 6abcbb58712a 90: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] discards 49b4ada55151 89: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] discards 5ce2eacab4da 88: onsuccess: #825: 1: Success after binutils/gcc/linux/g [...] discards 94bbf066e3bc 87: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] discards 2a6e6598264d 86: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] discards 5c529dfa3a57 85: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] discards 520ea277e5bd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] discards b3253fc0cc55 83: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] discards 77ac7852d246 82: onsuccess: #819: 1: Success after binutils/gcc/linux/g [...] discards a0572be38be8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/g [...] discards 3f5202ef17e9 80: onsuccess: #817: 1: Success after binutils/gcc/linux/g [...] discards b18e27f329f2 79: onsuccess: #816: 1: Success after binutils/gcc/linux/g [...] discards fac912fb1bc3 78: onsuccess: #815: 1: Success after binutils/gcc/linux/g [...] discards 1a9f08f804d2 77: onsuccess: #814: 1: Success after binutils/gcc/linux/g [...] discards 6d2f47b3a063 76: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] discards f5e9b4f1d96c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] discards 4bbb8af650e5 74: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] discards b098af5e22f9 73: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] discards 5ff2cbae832a 72: onsuccess: #809: 1: Success after binutils/gcc/linux/g [...] discards ce5e494b352e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/g [...] discards a62bd6aae765 70: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] discards 77ede52d4c8b 69: onsuccess: #806: 1: Success after binutils/gcc/linux/g [...] discards a1ceb19b4657 68: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] discards 66769c4ba918 67: onsuccess: #804: 1: Success after binutils/gcc/linux/g [...] discards 6a34e61aee27 66: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] discards c8714d65e525 65: onsuccess: #802: 1: Success after binutils/gcc/linux/g [...] discards 94e69529bd55 64: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] discards ca68c5fb0006 63: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] discards 2390c71ed5a4 62: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] discards bdfa50354f04 61: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] discards bfaf9eacd4d3 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/g [...] discards 9cc0b5d39d5c 59: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] discards 4f1e70e7eb1a 58: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] discards 542ada0e68bc 57: onsuccess: #794: 1: Success after binutils/gcc/linux/g [...] discards 03166b882100 56: onsuccess: #793: 1: Success after binutils/gcc/linux/g [...] discards 8f6e6efe8f07 55: onsuccess: #792: 1: Success after binutils/gcc/linux/g [...] discards 058fbd3a444a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/g [...] discards d04d2f4d744b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/g [...] discards 989149b3bb22 52: onsuccess: #789: 1: Success after binutils/gcc/linux/g [...] discards 3bf71fe45954 51: onsuccess: #788: 1: Success after binutils/gcc/linux/g [...] discards 62eabc7b454e 50: onsuccess: #787: 1: Success after binutils/gcc/linux/g [...] discards f71b9febad57 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 63b9c67e5edb 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 5c0c15deb56b 47: onsuccess: #780: 1: Success after binutils/gcc/linux/g [...] discards 31829f6d11fa 46: onsuccess: #779: 1: Success after binutils/gcc/linux/g [...] discards f74ed0f6993e 45: onsuccess: #778: 1: Success after binutils/gcc/linux/g [...] discards 29f5cf20a0f7 44: onsuccess: #777: 1: Success after binutils/gcc/linux/g [...] discards e5a687314258 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/g [...] discards 2db70cd37857 42: onsuccess: #775: 1: Success after binutils/gcc/linux/g [...] discards 86ee1da059d7 41: onsuccess: #774: 1: Success after binutils/gcc/linux/g [...] discards 278ab2f351a7 40: onsuccess: #773: 1: Success after binutils/gcc/linux/g [...] discards b0dd20ec0fe4 39: onsuccess: #772: 1: Success after binutils/gcc/linux/g [...] discards cecef3f2daf9 38: onsuccess: #771: 1: Success after binutils/gcc/linux/g [...] discards eeb43d0c13ea 37: onsuccess: #770: 1: Success after binutils/gcc/linux/g [...] discards 87695ceb80bd 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 [...] discards b2c0ceda00a4 35: onsuccess: #768: 1: Success after binutils/gcc/linux/g [...] discards c130043281cb 34: onsuccess: #767: 1: Success after binutils/gcc/linux/g [...] discards 596656f2d565 33: onsuccess: #766: 1: Success after binutils/gcc/linux/g [...] new bd69dd1b6b7f 33: onsuccess: #766: 1: Success after binutils/gcc/linux/g [...] new 27d65ae2e633 34: onsuccess: #767: 1: Success after binutils/gcc/linux/g [...] new ab68993c2ade 35: onsuccess: #768: 1: Success after binutils/gcc/linux/g [...] new 5a64352c09aa 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 [...] new e9d5c32d7a62 37: onsuccess: #770: 1: Success after binutils/gcc/linux/g [...] new 81647035f936 38: onsuccess: #771: 1: Success after binutils/gcc/linux/g [...] new 5304389251cd 39: onsuccess: #772: 1: Success after binutils/gcc/linux/g [...] new da0ef418f2e5 40: onsuccess: #773: 1: Success after binutils/gcc/linux/g [...] new 375eefd0baf3 41: onsuccess: #774: 1: Success after binutils/gcc/linux/g [...] new e839f9547ace 42: onsuccess: #775: 1: Success after binutils/gcc/linux/g [...] new 246b59ce80c4 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/g [...] new 338de786816c 44: onsuccess: #777: 1: Success after binutils/gcc/linux/g [...] new 0fec7ecd60b9 45: onsuccess: #778: 1: Success after binutils/gcc/linux/g [...] new 0c5d83aa4d53 46: onsuccess: #779: 1: Success after binutils/gcc/linux/g [...] new 674e44e682a3 47: onsuccess: #780: 1: Success after binutils/gcc/linux/g [...] new 8095efef9a95 48: onsuccess: #782: 1: Success after binutils: 8 commits new 4c2c5da32801 49: onsuccess: #785: 1: Success after binutils: 12 commits new 36689f0cfe3c 50: onsuccess: #787: 1: Success after binutils/gcc/linux/g [...] new 22e1ee8b89e5 51: onsuccess: #788: 1: Success after binutils/gcc/linux/g [...] new 508bca81723b 52: onsuccess: #789: 1: Success after binutils/gcc/linux/g [...] new bf1fe12f5dd5 53: onsuccess: #790: 1: Success after binutils/gcc/linux/g [...] new 65bf19a0db05 54: onsuccess: #791: 1: Success after binutils/gcc/linux/g [...] new 9cff69a8203c 55: onsuccess: #792: 1: Success after binutils/gcc/linux/g [...] new 93ecab29ff82 56: onsuccess: #793: 1: Success after binutils/gcc/linux/g [...] new 925941682607 57: onsuccess: #794: 1: Success after binutils/gcc/linux/g [...] new 5580696988cd 58: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] new c5d38d06dd30 59: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] new b5dc836b59a7 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/g [...] new c51e0a5f89d7 61: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] new 7b87c2fbce8f 62: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] new 65b52a5e9c0b 63: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] new 927bf970f49e 64: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] new ffcc9ef65ce7 65: onsuccess: #802: 1: Success after binutils/gcc/linux/g [...] new ade6a2ac2e93 66: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] new 789849d4f66b 67: onsuccess: #804: 1: Success after binutils/gcc/linux/g [...] new d181d033fdfe 68: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] new f697697123fd 69: onsuccess: #806: 1: Success after binutils/gcc/linux/g [...] new 51ea99acd448 70: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] new 9fca8b692e02 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/g [...] new 628818ef49f0 72: onsuccess: #809: 1: Success after binutils/gcc/linux/g [...] new 7304346bb4b0 73: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] new a0a60a30bf59 74: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] new e71e1b6307a6 75: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] new ede35b7f1cb4 76: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] new 1d15bdbf04cf 77: onsuccess: #814: 1: Success after binutils/gcc/linux/g [...] new 880bd3c26409 78: onsuccess: #815: 1: Success after binutils/gcc/linux/g [...] new 9f21f75db370 79: onsuccess: #816: 1: Success after binutils/gcc/linux/g [...] new def9ceb2e600 80: onsuccess: #817: 1: Success after binutils/gcc/linux/g [...] new 58ab8e05f267 81: onsuccess: #818: 1: Success after binutils/gcc/linux/g [...] new 1a3d15dac8fa 82: onsuccess: #819: 1: Success after binutils/gcc/linux/g [...] new 7b47f0fde196 83: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] new 7f4c5c874d44 84: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] new adede0396a70 85: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] new a786031d1983 86: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] new 0f84d7d1dcdd 87: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] new c59798e08641 88: onsuccess: #825: 1: Success after binutils/gcc/linux/g [...] new 98469d5f99fc 89: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] new 2c56f6ba3b6c 90: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] new 1e1aed82e5ed 91: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] new 418be8dc3465 92: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] new eb0828b656ad 93: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] new fae4a08e2809 94: onsuccess: #832: 1: Success after binutils: 5 commits new 1986ba9aacf6 95: onsuccess: #835: 1: Success after binutils: 3 commits new 563e58ab3b84 96: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] new a07132afa8b1 97: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] new 989894dc0fe6 98: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] new 1c9b0f0d3e59 99: onsuccess: #840: 1: Success after binutils/gcc/linux/g [...] new 0ed91aac84f4 100: onsuccess: #841: 1: Success after binutils/gcc/linux/ [...] new 7cb44923d978 101: onsuccess: #842: 1: Success after binutils/gcc/linux/ [...] new 96d1a19dd98a 102: onsuccess: #843: 1: Success after binutils/gcc/linux/ [...] new cc8366115c48 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 5 [...] new 2cb7c522db2d 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 6 [...] new bfddafce3347 105: onsuccess: #846: 1: Success after binutils/gcc/linux/ [...] new fee4496bbb00 106: onsuccess: #847: 1: Success after binutils/gcc/linux/ [...] new 838b66bf868f 107: onsuccess: #849: 1: Success after binutils: 5 commits new 800dcd390b6e 108: onsuccess: #850: 1: Success after gcc: 2 commits new d03a67202752 109: onsuccess: #852: 1: Success after binutils/gcc/linux/ [...] new 23e587552656 110: onsuccess: #853: 1: Success after binutils/gcc/linux/ [...] new 81d8e2705d04 111: onsuccess: #854: 1: Success after binutils/gcc/linux/ [...] new db7c0c61ef16 112: onsuccess: #855: 1: Success after binutils/gcc/linux/ [...] new e202054f5307 113: onsuccess: #856: 1: Success after binutils/gcc/linux/ [...] new dc08643f7434 114: onsuccess: #857: 1: Success after binutils/gcc/linux/ [...] new f217ed25f590 115: onsuccess: #858: 1: Success after binutils/gcc/linux/ [...] new f714dc57d65c 116: onsuccess: #859: 1: Success after binutils/gcc/linux/ [...] new 167aede51582 117: onsuccess: #861: 1: Success after binutils: 18 commits new 9dbd15b77470 118: onsuccess: #863: 1: Success after linux: 12 commits new 39729cd83401 119: onsuccess: #864: 1: Success after binutils/gcc/linux/ [...] new 0fa44e5129ba 120: onsuccess: #865: 1: Success after binutils/gcc/linux/ [...] new 366650701cd3 121: onsuccess: #866: 1: Success after binutils/gcc/linux/ [...] new e9453833e0e7 122: onsuccess: #867: 1: Success after binutils/gcc/linux/ [...] new 3754b08e7b1d 123: onsuccess: #868: 1: Success after binutils/gcc/linux/ [...] new 957bd3f22e92 124: onsuccess: #869: 1: Success after binutils/gcc/linux/ [...] new a29c60738a7c 125: onsuccess: #871: 1: Success after binutils: 26 commits new 8ba61e98848f 126: onsuccess: #873: 1: Success after glibc: 2 commits new d47a33246e3b 127: onsuccess: #874: 1: Success after linux: 219 commits new be2ee99674be 128: onsuccess: #876: 1: Success after binutils: 12 commits new 4ba25fd69773 129: onsuccess: #878: 1: Success after linux: 3008 commits new 297fd3c17816 130: onsuccess: #879: 1: Success after binutils/gcc/linux/ [...] new b0097f590674 131: onsuccess: #880: 1: Success after binutils/gcc/linux/ [...] new b4f7244f4af5 132: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] new abffac468fc0 133: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] new 29f8cf0bebbd 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 1 [...]

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 (5e0321de6e66) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]

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 1752 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 40388 -> 39580 bytes 04-build_abe-gcc/console.log.xz | Bin 215716 -> 213428 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8568 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 244260 -> 243672 bytes 08-build_abe-gdb/console.log.xz | Bin 39840 -> 39336 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3832 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2980 -> 2604 bytes 11-check_regression/console.log.xz | Bin 6808 -> 5776 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 137 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 38 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 27 + sumfiles/g++.log.xz | Bin 3773596 -> 3769764 bytes sumfiles/g++.sum | 116 +- sumfiles/gcc.log.xz | Bin 3291492 -> 3315620 bytes sumfiles/gcc.sum | 5082 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1087616 -> 1081820 bytes sumfiles/gfortran.sum | 98 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232352 -> 232456 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 447492 -> 456808 bytes sumfiles/libstdc++.sum | 10 +- 41 files changed, 2860 insertions(+), 2831 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions