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 7f625878b8fa 132: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] discards 1f89f2f1ed5d 131: onsuccess: #880: 1: Success after binutils/gcc/linux/ [...] discards 0df9cc831123 130: onsuccess: #879: 1: Success after binutils/gcc/linux/ [...] discards e9f5a64ce225 129: onsuccess: #878: 1: Success after linux: 3008 commits discards c249ce651269 128: onsuccess: #876: 1: Success after binutils: 12 commits discards edf637a87745 127: onsuccess: #874: 1: Success after linux: 219 commits discards 96a91418f12d 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 55da97684a92 125: onsuccess: #871: 1: Success after binutils: 26 commits discards a9b2db6d5fc6 124: onsuccess: #869: 1: Success after binutils/gcc/linux/ [...] discards f6af8d0b87a9 123: onsuccess: #868: 1: Success after binutils/gcc/linux/ [...] discards c6c4ea028737 122: onsuccess: #867: 1: Success after binutils/gcc/linux/ [...] discards 092f28844d67 121: onsuccess: #866: 1: Success after binutils/gcc/linux/ [...] discards 9fd35c7e8780 120: onsuccess: #865: 1: Success after binutils/gcc/linux/ [...] discards 91388531f572 119: onsuccess: #864: 1: Success after binutils/gcc/linux/ [...] discards a5f7463e1f94 118: onsuccess: #863: 1: Success after linux: 12 commits discards 73add8d90429 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 6847ca546192 116: onsuccess: #859: 1: Success after binutils/gcc/linux/ [...] discards 8d9672b5f456 115: onsuccess: #858: 1: Success after binutils/gcc/linux/ [...] discards 96d7c7a5c77c 114: onsuccess: #857: 1: Success after binutils/gcc/linux/ [...] discards 5aaecd540044 113: onsuccess: #856: 1: Success after binutils/gcc/linux/ [...] discards e6e581b774e8 112: onsuccess: #855: 1: Success after binutils/gcc/linux/ [...] discards ad71ce499c0c 111: onsuccess: #854: 1: Success after binutils/gcc/linux/ [...] discards 3fd15ecf4a4d 110: onsuccess: #853: 1: Success after binutils/gcc/linux/ [...] discards 44ba04c1ead4 109: onsuccess: #852: 1: Success after binutils/gcc/linux/ [...] discards cf4c73b3c618 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 66d9260407d8 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 0fd5ef49e1fb 106: onsuccess: #847: 1: Success after binutils/gcc/linux/ [...] discards 62afc4106031 105: onsuccess: #846: 1: Success after binutils/gcc/linux/ [...] discards c6cb31397127 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 6 [...] discards a73152fd0bbd 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 5 [...] discards a89439238bb8 102: onsuccess: #843: 1: Success after binutils/gcc/linux/ [...] discards 189b9c147f11 101: onsuccess: #842: 1: Success after binutils/gcc/linux/ [...] discards abed5775fec7 100: onsuccess: #841: 1: Success after binutils/gcc/linux/ [...] discards 9b56537b8862 99: onsuccess: #840: 1: Success after binutils/gcc/linux/g [...] discards 91aa4f396840 98: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] discards 1b7bfac8b5ba 97: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] discards 7bb7e1db1c4b 96: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] discards 03c75c417196 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 83ae852c2958 94: onsuccess: #832: 1: Success after binutils: 5 commits discards a350fa4f35fd 93: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] discards b36ceca9f40a 92: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] discards 07aecbbc91d1 91: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] discards 1728f55c1734 90: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] discards aafa0f53ea0b 89: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] discards e571bae1d6c5 88: onsuccess: #825: 1: Success after binutils/gcc/linux/g [...] discards fe6049befb2b 87: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] discards 4b896d60c3d9 86: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] discards 578ab523e197 85: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] discards a528b6fba09e 84: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] discards 90abfb4a921a 83: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] discards 4b1150f656a2 82: onsuccess: #819: 1: Success after binutils/gcc/linux/g [...] discards f4f1170204d8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/g [...] discards 05588a7698d8 80: onsuccess: #817: 1: Success after binutils/gcc/linux/g [...] discards bff8362e0e02 79: onsuccess: #816: 1: Success after binutils/gcc/linux/g [...] discards 97cd48edd9a8 78: onsuccess: #815: 1: Success after binutils/gcc/linux/g [...] discards 8a9def320141 77: onsuccess: #814: 1: Success after binutils/gcc/linux/g [...] discards 24ea8c2a1079 76: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] discards 441bba26fb6d 75: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] discards 5191e3f68403 74: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] discards ea46a6a9c395 73: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] discards b5119c92f9bc 72: onsuccess: #809: 1: Success after binutils/gcc/linux/g [...] discards bbf0552d87ab 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/g [...] discards 37e2e08f6515 70: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] discards 71b081417605 69: onsuccess: #806: 1: Success after binutils/gcc/linux/g [...] discards 1621e774ae25 68: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] discards 13367350a9a6 67: onsuccess: #804: 1: Success after binutils/gcc/linux/g [...] discards 1334e1a10683 66: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] discards b8161cf0ffb9 65: onsuccess: #802: 1: Success after binutils/gcc/linux/g [...] discards 1ce7bd5d6bd1 64: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] discards d4bf740c8d40 63: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] discards 8842053ef353 62: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] discards 7777f99b47ad 61: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] discards 94e04484712b 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/g [...] discards ca92e67c94d1 59: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] discards 90070c23ca3c 58: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] discards 0d5c713ee631 57: onsuccess: #794: 1: Success after binutils/gcc/linux/g [...] discards 7469493d9bb2 56: onsuccess: #793: 1: Success after binutils/gcc/linux/g [...] discards 5bc08b461b3a 55: onsuccess: #792: 1: Success after binutils/gcc/linux/g [...] discards bdd440e24b65 54: onsuccess: #791: 1: Success after binutils/gcc/linux/g [...] discards d07305c0b7f2 53: onsuccess: #790: 1: Success after binutils/gcc/linux/g [...] discards 37d9a450ee15 52: onsuccess: #789: 1: Success after binutils/gcc/linux/g [...] discards 7d0db5c52b53 51: onsuccess: #788: 1: Success after binutils/gcc/linux/g [...] discards 7fd6fba3642e 50: onsuccess: #787: 1: Success after binutils/gcc/linux/g [...] discards b4d298ab396d 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 5e70ccb1caf5 48: onsuccess: #782: 1: Success after binutils: 8 commits discards f9a5fc894655 47: onsuccess: #780: 1: Success after binutils/gcc/linux/g [...] discards b728b5d81df0 46: onsuccess: #779: 1: Success after binutils/gcc/linux/g [...] discards d1c9cc61b4d2 45: onsuccess: #778: 1: Success after binutils/gcc/linux/g [...] discards 0773cfd78833 44: onsuccess: #777: 1: Success after binutils/gcc/linux/g [...] discards 755c804a4427 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/g [...] discards 007b72f2e4e7 42: onsuccess: #775: 1: Success after binutils/gcc/linux/g [...] discards f9e6667e2140 41: onsuccess: #774: 1: Success after binutils/gcc/linux/g [...] discards f3d48a0735bc 40: onsuccess: #773: 1: Success after binutils/gcc/linux/g [...] discards b2ca7faa67d0 39: onsuccess: #772: 1: Success after binutils/gcc/linux/g [...] discards 4b259a1e5dda 38: onsuccess: #771: 1: Success after binutils/gcc/linux/g [...] discards 26c359e7b743 37: onsuccess: #770: 1: Success after binutils/gcc/linux/g [...] discards 0b5d47457436 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 [...] discards f659df71a32f 35: onsuccess: #768: 1: Success after binutils/gcc/linux/g [...] discards 36cbf598ad19 34: onsuccess: #767: 1: Success after binutils/gcc/linux/g [...] discards f02b4d5b8841 33: onsuccess: #766: 1: Success after binutils/gcc/linux/g [...] discards d808a32d6c98 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/g [...] new 79ffbbe5849d 32: onsuccess: #765: 1: Success after binutils/gcc/glibc/g [...] new 596656f2d565 33: onsuccess: #766: 1: Success after binutils/gcc/linux/g [...] new c130043281cb 34: onsuccess: #767: 1: Success after binutils/gcc/linux/g [...] new b2c0ceda00a4 35: onsuccess: #768: 1: Success after binutils/gcc/linux/g [...] new 87695ceb80bd 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 [...] new eeb43d0c13ea 37: onsuccess: #770: 1: Success after binutils/gcc/linux/g [...] new cecef3f2daf9 38: onsuccess: #771: 1: Success after binutils/gcc/linux/g [...] new b0dd20ec0fe4 39: onsuccess: #772: 1: Success after binutils/gcc/linux/g [...] new 278ab2f351a7 40: onsuccess: #773: 1: Success after binutils/gcc/linux/g [...] new 86ee1da059d7 41: onsuccess: #774: 1: Success after binutils/gcc/linux/g [...] new 2db70cd37857 42: onsuccess: #775: 1: Success after binutils/gcc/linux/g [...] new e5a687314258 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/g [...] new 29f5cf20a0f7 44: onsuccess: #777: 1: Success after binutils/gcc/linux/g [...] new f74ed0f6993e 45: onsuccess: #778: 1: Success after binutils/gcc/linux/g [...] new 31829f6d11fa 46: onsuccess: #779: 1: Success after binutils/gcc/linux/g [...] new 5c0c15deb56b 47: onsuccess: #780: 1: Success after binutils/gcc/linux/g [...] new 63b9c67e5edb 48: onsuccess: #782: 1: Success after binutils: 8 commits new f71b9febad57 49: onsuccess: #785: 1: Success after binutils: 12 commits new 62eabc7b454e 50: onsuccess: #787: 1: Success after binutils/gcc/linux/g [...] new 3bf71fe45954 51: onsuccess: #788: 1: Success after binutils/gcc/linux/g [...] new 989149b3bb22 52: onsuccess: #789: 1: Success after binutils/gcc/linux/g [...] new d04d2f4d744b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/g [...] new 058fbd3a444a 54: onsuccess: #791: 1: Success after binutils/gcc/linux/g [...] new 8f6e6efe8f07 55: onsuccess: #792: 1: Success after binutils/gcc/linux/g [...] new 03166b882100 56: onsuccess: #793: 1: Success after binutils/gcc/linux/g [...] new 542ada0e68bc 57: onsuccess: #794: 1: Success after binutils/gcc/linux/g [...] new 4f1e70e7eb1a 58: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] new 9cc0b5d39d5c 59: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] new bfaf9eacd4d3 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/g [...] new bdfa50354f04 61: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] new 2390c71ed5a4 62: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] new ca68c5fb0006 63: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] new 94e69529bd55 64: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] new c8714d65e525 65: onsuccess: #802: 1: Success after binutils/gcc/linux/g [...] new 6a34e61aee27 66: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] new 66769c4ba918 67: onsuccess: #804: 1: Success after binutils/gcc/linux/g [...] new a1ceb19b4657 68: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] new 77ede52d4c8b 69: onsuccess: #806: 1: Success after binutils/gcc/linux/g [...] new a62bd6aae765 70: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] new ce5e494b352e 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/g [...] new 5ff2cbae832a 72: onsuccess: #809: 1: Success after binutils/gcc/linux/g [...] new b098af5e22f9 73: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] new 4bbb8af650e5 74: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] new f5e9b4f1d96c 75: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] new 6d2f47b3a063 76: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] new 1a9f08f804d2 77: onsuccess: #814: 1: Success after binutils/gcc/linux/g [...] new fac912fb1bc3 78: onsuccess: #815: 1: Success after binutils/gcc/linux/g [...] new b18e27f329f2 79: onsuccess: #816: 1: Success after binutils/gcc/linux/g [...] new 3f5202ef17e9 80: onsuccess: #817: 1: Success after binutils/gcc/linux/g [...] new a0572be38be8 81: onsuccess: #818: 1: Success after binutils/gcc/linux/g [...] new 77ac7852d246 82: onsuccess: #819: 1: Success after binutils/gcc/linux/g [...] new b3253fc0cc55 83: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] new 520ea277e5bd 84: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] new 5c529dfa3a57 85: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] new 2a6e6598264d 86: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] new 94bbf066e3bc 87: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] new 5ce2eacab4da 88: onsuccess: #825: 1: Success after binutils/gcc/linux/g [...] new 49b4ada55151 89: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] new 6abcbb58712a 90: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] new 84036d7417ff 91: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] new 8855e87bd871 92: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] new abb6ca043624 93: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] new f24d7e217214 94: onsuccess: #832: 1: Success after binutils: 5 commits new 52573bb364ba 95: onsuccess: #835: 1: Success after binutils: 3 commits new 89a0617acc2b 96: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] new 2ba0e9ef64b6 97: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] new 81ebcf37e46e 98: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] new 9d99aea9449d 99: onsuccess: #840: 1: Success after binutils/gcc/linux/g [...] new 44ba5237a355 100: onsuccess: #841: 1: Success after binutils/gcc/linux/ [...] new 0f829e5d1e9e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/ [...] new 923450ae222e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/ [...] new 0136f8e9a48e 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 5 [...] new f12002ffb47f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 6 [...] new b287ac99fb5a 105: onsuccess: #846: 1: Success after binutils/gcc/linux/ [...] new 54ecb52bc97f 106: onsuccess: #847: 1: Success after binutils/gcc/linux/ [...] new a9b98a70ebc5 107: onsuccess: #849: 1: Success after binutils: 5 commits new 1c6a30a2dd67 108: onsuccess: #850: 1: Success after gcc: 2 commits new bd9c2d3dca1a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/ [...] new 0cce8bbb8992 110: onsuccess: #853: 1: Success after binutils/gcc/linux/ [...] new d442b041a0be 111: onsuccess: #854: 1: Success after binutils/gcc/linux/ [...] new 789bc7b4a658 112: onsuccess: #855: 1: Success after binutils/gcc/linux/ [...] new fdf049936e5c 113: onsuccess: #856: 1: Success after binutils/gcc/linux/ [...] new f201ae473f57 114: onsuccess: #857: 1: Success after binutils/gcc/linux/ [...] new 7babce8f62e2 115: onsuccess: #858: 1: Success after binutils/gcc/linux/ [...] new b869f9191c5f 116: onsuccess: #859: 1: Success after binutils/gcc/linux/ [...] new c47602f86a58 117: onsuccess: #861: 1: Success after binutils: 18 commits new f79c3d121b38 118: onsuccess: #863: 1: Success after linux: 12 commits new c999135a3dd4 119: onsuccess: #864: 1: Success after binutils/gcc/linux/ [...] new 05aee1a0146a 120: onsuccess: #865: 1: Success after binutils/gcc/linux/ [...] new 1259d5fb9a8a 121: onsuccess: #866: 1: Success after binutils/gcc/linux/ [...] new 2c115de04fe5 122: onsuccess: #867: 1: Success after binutils/gcc/linux/ [...] new b1b2738c77de 123: onsuccess: #868: 1: Success after binutils/gcc/linux/ [...] new 7df7160e8544 124: onsuccess: #869: 1: Success after binutils/gcc/linux/ [...] new aee078522342 125: onsuccess: #871: 1: Success after binutils: 26 commits new f6e1a362aed2 126: onsuccess: #873: 1: Success after glibc: 2 commits new 7d6eb0e7da34 127: onsuccess: #874: 1: Success after linux: 219 commits new f9a0e4bbd76f 128: onsuccess: #876: 1: Success after binutils: 12 commits new f4e739c2c37e 129: onsuccess: #878: 1: Success after linux: 3008 commits new 9d75104dd4a4 130: onsuccess: #879: 1: Success after binutils/gcc/linux/ [...] new 24e9ea2f5f5a 131: onsuccess: #880: 1: Success after binutils/gcc/linux/ [...] new c7c9af9a1790 132: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] new 5e0321de6e66 133: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...]

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 (7f625878b8fa) \ 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 1748 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 39808 -> 40388 bytes 04-build_abe-gcc/console.log.xz | Bin 214540 -> 215716 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9780 -> 8568 bytes 07-build_abe-glibc/console.log.xz | Bin 243544 -> 244260 bytes 08-build_abe-gdb/console.log.xz | Bin 39260 -> 39840 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3840 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2488 -> 2980 bytes 11-check_regression/console.log.xz | Bin 7388 -> 6808 bytes 11-check_regression/mail-body.txt | 37 - 11-check_regression/results.compare | 41 +- 11-check_regression/results.compare2 | 220 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 39 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- sumfiles/g++.log.xz | Bin 3745796 -> 3773596 bytes sumfiles/g++.sum | 144 +- sumfiles/gcc.log.xz | Bin 3307476 -> 3291492 bytes sumfiles/gcc.sum | 5153 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1089368 -> 1087616 bytes sumfiles/gfortran.sum | 92 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232152 -> 232352 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 450744 -> 447492 bytes sumfiles/libstdc++.sum | 21 +- 38 files changed, 2887 insertions(+), 2970 deletions(-)