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 b1eb5c7935 163: onsuccess: #914: 1: Success after binutils/gcc/linux/gl [...] discards 678072178d 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] discards d8f296c5f9 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 454853e9cb 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] discards b206aa3798 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] discards 0b730d5a66 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] discards a8d064e8c2 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards ee9d26b03e 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards f7fcfe4f60 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards da5d11368c 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards 1bbabbafc3 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards 62107fa404 152: onsuccess: #903: 1: Success after linux: 22 commits discards 10d2f3c69d 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 3262609b19 150: onsuccess: #900: 1: Success after gcc: 11 commits discards fdea3c25a0 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 845a7c464e 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 592a560006 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards 4458508fa3 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards 5c2a0eb48f 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards f40e5ed754 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards fac28dd694 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards a1bcacf487 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 93faa3e75e 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 078eeabc25 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 8b4ea7b322 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards b5f20843d4 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards f701b3ed4f 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 82826dcee5 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards b110a3636f 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards f8fd6be15f 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards 04a1281567 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 1ab8e212c9 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 524b0193ea 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 927022b4a5 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 9943f70c0d 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 15cfb9a113 128: onsuccess: #876: 1: Success after binutils: 12 commits discards f0ba803181 127: onsuccess: #874: 1: Success after linux: 219 commits discards 2c08489cd6 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 8185d1415d 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 24f919ae80 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 27a64e41a0 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 640f3ef7fe 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards a93b786ad5 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 955ac5523e 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 0bfc18e2c0 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards bd151b1116 118: onsuccess: #863: 1: Success after linux: 12 commits discards 1551cbc682 117: onsuccess: #861: 1: Success after binutils: 18 commits discards ce70f1acec 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 78fdf0bcbb 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 3e041eae06 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards bea374cb58 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 48511c3b30 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 073fe14c08 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards 90e3bd6833 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards ed00c807b6 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards ae85a83794 108: onsuccess: #850: 1: Success after gcc: 2 commits discards ad98fedeed 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 28274dcf04 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 983a901354 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 74b2d70571 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 7a9a9b9e94 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards ec460e3fce 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards bf68cb95b1 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 316a6bc201 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards a722bf43e7 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards d74de2f665 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 7a2e19314a 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards 708bc74931 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 5fe4f79292 95: onsuccess: #835: 1: Success after binutils: 3 commits discards f1634d7dad 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 7dc74048f5 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 58b5674516 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 9cb1c09ed1 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards a6d1b4849a 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 1f525d04ab 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 269fc13eeb 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 98e50dcb4d 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 542e20359f 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 53fc00031b 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards cf3abfb75a 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 9151b02a70 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards 094e81a5ed 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards b789dee92a 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 059a20c640 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards a5d631440e 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 369855a277 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 1b6d6c5b5a 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards e7b8cd637d 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 1658505864 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards bf24d2ff3c 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 7b7a0d9a29 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards 9c269d9dad 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 6d4639021c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards 2feda143f2 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards d667668a47 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 3621c71859 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 1f81bab7c3 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 2b3acd3643 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards e1468c74f4 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 98be176f88 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 72cdd5235d 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 5ec6878e8a 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 7186c268de 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 36a8821e39 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 5f69bec7aa 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 17cf4fa7b3 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 24f68f29a2 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new ade90f4720 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new 1fb071e3a3 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new c8d6db700c 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new b0e5b4db80 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 2c8db1d6a1 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 98c3504654 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 039c627799 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new b4f4305233 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 52e41111a5 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new dab824ccba 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 4d78dca1cb 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new bbcb3bd52b 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 3951c9b8db 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new 8e475aaede 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 87d5204ce5 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new b82dc92cf6 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new 1f2cbb44c3 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 4f5c9068be 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 1436dfe078 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 96d963610f 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new d28add0ca2 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new cbbcf149c1 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new e25e235d08 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new f4fb7f07d5 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 6f51d467f0 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new f4df154887 94: onsuccess: #832: 1: Success after binutils: 5 commits new afc6be8932 95: onsuccess: #835: 1: Success after binutils: 3 commits new 7b2deef19f 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new b267cc3d50 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new c6969e40c7 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new a5344e190e 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new d80c340deb 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new a56ef82ee5 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 5f569943c9 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 7d4d3faaa7 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new edf256b350 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new d95f1eafc0 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new d9d3ac0044 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new c0059c996d 107: onsuccess: #849: 1: Success after binutils: 5 commits new bef04f5519 108: onsuccess: #850: 1: Success after gcc: 2 commits new eb47c18d9e 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new d701332e5b 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new daa3ab5991 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new ea6580e828 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new f3475edf64 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new e9491effcf 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 22085b112b 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new b1cbb561fd 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 51e307ab54 117: onsuccess: #861: 1: Success after binutils: 18 commits new 573b02836e 118: onsuccess: #863: 1: Success after linux: 12 commits new cabb308076 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new e03d5e1d6f 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 55dc28ab69 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 15eea36d02 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 1edcc9013a 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 40bc0adbf3 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new efa1a353f6 125: onsuccess: #871: 1: Success after binutils: 26 commits new 178539176c 126: onsuccess: #873: 1: Success after glibc: 2 commits new 6be7ae8482 127: onsuccess: #874: 1: Success after linux: 219 commits new cce634fee1 128: onsuccess: #876: 1: Success after binutils: 12 commits new c90838b631 129: onsuccess: #878: 1: Success after linux: 3008 commits new 46669bb16f 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 77e084c275 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new b7def3dac2 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 8cd54219a5 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 0aae4c50c7 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new a872d0e404 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 84d7701b95 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 61a7fec923 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new bcd26d8fd4 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 98faa44c58 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new da7a90e71f 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 2c04dc2c6a 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new e30b9471c5 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new d88ba257aa 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 1f66dd6bc1 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new 44ac6788ec 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 6ce33b8973 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 3f5aee047d 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new c6fab153dc 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new f7aac07811 149: onsuccess: #899: 1: Success after binutils: 15 commits new 20d9f4506f 150: onsuccess: #900: 1: Success after gcc: 11 commits new a862d0f824 151: onsuccess: #902: 1: Success after glibc: 8 commits new 334d67ce79 152: onsuccess: #903: 1: Success after linux: 22 commits new 57e0689095 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new 0b28346544 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new e718c708e5 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new dbe2a68679 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new 9e7e3ffdf9 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new 8f418d4041 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] new 5b45f8c83d 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] new 8f1af47734 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] new d03df2b1cc 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 2d4a4424f2 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] new f406bb535f 163: onsuccess: #914: 1: Success after binutils/gcc/linux/gl [...] new c76042777d 164: onsuccess: #915: 1: Success after binutils/gcc/linux/gl [...]

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 (b1eb5c7935) \ 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 1764 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 39516 -> 39276 bytes 04-build_abe-gcc/console.log.xz | Bin 213636 -> 214276 bytes 06-build_abe-linux/console.log.xz | Bin 8260 -> 8548 bytes 07-build_abe-glibc/console.log.xz | Bin 244412 -> 246432 bytes 08-build_abe-gdb/console.log.xz | Bin 39404 -> 39480 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3852 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2568 -> 2544 bytes 11-check_regression/console.log.xz | Bin 7540 -> 7936 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 75 +- 11-check_regression/results.compare | 17 +- 11-check_regression/results.compare2 | 287 +- 11-check_regression/results.regressions | 41 - 12-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 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 77 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 41 - sumfiles/g++.log.xz | Bin 3743712 -> 3763128 bytes sumfiles/g++.sum | 108 +- sumfiles/gcc.log.xz | Bin 3290612 -> 3307164 bytes sumfiles/gcc.sum | 5003 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1084068 -> 1081316 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2272 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 232368 -> 232340 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 454076 -> 456708 bytes sumfiles/libstdc++.sum | 2 +- 42 files changed, 2934 insertions(+), 2857 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions