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 fa2721d047da 135: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...] discards 4f225209b68b 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 1 [...] discards 6229f222bbf5 133: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] discards 04d297cfecb4 132: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] discards 50c50763e2a5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/ [...] discards ee3232e45cee 130: onsuccess: #879: 1: Success after binutils/gcc/linux/ [...] discards 53b61a23ec4f 129: onsuccess: #878: 1: Success after linux: 3008 commits discards a7d8dd5fd869 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 17f5dd6d7d81 127: onsuccess: #874: 1: Success after linux: 219 commits discards 3a7ca0843c7a 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 035455fcafe4 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 4108d2964d0a 124: onsuccess: #869: 1: Success after binutils/gcc/linux/ [...] discards 2d455fcfe55c 123: onsuccess: #868: 1: Success after binutils/gcc/linux/ [...] discards 1dbfbd94370e 122: onsuccess: #867: 1: Success after binutils/gcc/linux/ [...] discards 57737eca9f27 121: onsuccess: #866: 1: Success after binutils/gcc/linux/ [...] discards 2a761ca35529 120: onsuccess: #865: 1: Success after binutils/gcc/linux/ [...] discards 8026fe233b03 119: onsuccess: #864: 1: Success after binutils/gcc/linux/ [...] discards feb1beb9abd7 118: onsuccess: #863: 1: Success after linux: 12 commits discards 87d3f6de86f2 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 4b87ac400f88 116: onsuccess: #859: 1: Success after binutils/gcc/linux/ [...] discards ffd6308f4869 115: onsuccess: #858: 1: Success after binutils/gcc/linux/ [...] discards 31b78cb7308e 114: onsuccess: #857: 1: Success after binutils/gcc/linux/ [...] discards bc64cd9688eb 113: onsuccess: #856: 1: Success after binutils/gcc/linux/ [...] discards 47dd3d66bd91 112: onsuccess: #855: 1: Success after binutils/gcc/linux/ [...] discards d959eada4cfd 111: onsuccess: #854: 1: Success after binutils/gcc/linux/ [...] discards b6d989ba3a9e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/ [...] discards 809eb134e0de 109: onsuccess: #852: 1: Success after binutils/gcc/linux/ [...] discards 5ad52e24808f 108: onsuccess: #850: 1: Success after gcc: 2 commits discards d51b90481913 107: onsuccess: #849: 1: Success after binutils: 5 commits discards 672fa26de006 106: onsuccess: #847: 1: Success after binutils/gcc/linux/ [...] discards 20d648475947 105: onsuccess: #846: 1: Success after binutils/gcc/linux/ [...] discards 4b5d2ed38ca7 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 6 [...] discards d91dcdb7fd79 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 5 [...] discards d53ea38ad92f 102: onsuccess: #843: 1: Success after binutils/gcc/linux/ [...] discards a8807d904a86 101: onsuccess: #842: 1: Success after binutils/gcc/linux/ [...] discards 0d6afef12425 100: onsuccess: #841: 1: Success after binutils/gcc/linux/ [...] discards 39a5266f5a5c 99: onsuccess: #840: 1: Success after binutils/gcc/linux/g [...] discards bc9462e7ae14 98: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] discards de30c157e733 97: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] discards 45acb8c63d63 96: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] discards 1026c0f9940f 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 4f1fc9e656e7 94: onsuccess: #832: 1: Success after binutils: 5 commits discards 06d82db2b2a3 93: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] discards 817351a8d3d7 92: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] discards febc1dd8fea4 91: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] discards adb602b2f810 90: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] discards 0f95a123a087 89: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] discards bb71d72fc48c 88: onsuccess: #825: 1: Success after binutils/gcc/linux/g [...] discards cf47725837af 87: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] discards e8ec22173a86 86: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] discards 5a12882a6831 85: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] discards 8a40ca0a69f2 84: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] discards 26befe7db913 83: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] discards 8b1b59a6f2ee 82: onsuccess: #819: 1: Success after binutils/gcc/linux/g [...] discards 915d7819115f 81: onsuccess: #818: 1: Success after binutils/gcc/linux/g [...] discards f367900b0986 80: onsuccess: #817: 1: Success after binutils/gcc/linux/g [...] discards fb5f075bf568 79: onsuccess: #816: 1: Success after binutils/gcc/linux/g [...] discards 7bb65c0055fb 78: onsuccess: #815: 1: Success after binutils/gcc/linux/g [...] discards 203c48ecbc49 77: onsuccess: #814: 1: Success after binutils/gcc/linux/g [...] discards cc1c6f077140 76: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] discards 3beb943b0395 75: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] discards 62054ca27e84 74: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] discards 7e208cf144e9 73: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] discards ddf7680920ef 72: onsuccess: #809: 1: Success after binutils/gcc/linux/g [...] discards 0046ff88acee 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/g [...] discards 78d7728d7abd 70: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] discards b49305c7fae7 69: onsuccess: #806: 1: Success after binutils/gcc/linux/g [...] discards 5d93e9ca6550 68: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] discards 82dce8fad2b1 67: onsuccess: #804: 1: Success after binutils/gcc/linux/g [...] discards e2d239da1355 66: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] discards 2a4cf6ec4ca9 65: onsuccess: #802: 1: Success after binutils/gcc/linux/g [...] discards d3049e0e5eb8 64: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] discards 44547057e6ea 63: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] discards 407b4cdf4c90 62: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] discards 402d43aa34ba 61: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] discards f17dc64a1277 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/g [...] discards 6452b5281c24 59: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] discards 203614a80d48 58: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] discards ea94ddbf08dd 57: onsuccess: #794: 1: Success after binutils/gcc/linux/g [...] discards 47e0ce351e4c 56: onsuccess: #793: 1: Success after binutils/gcc/linux/g [...] discards 2f77e3cecc3d 55: onsuccess: #792: 1: Success after binutils/gcc/linux/g [...] discards 69f979f0e11c 54: onsuccess: #791: 1: Success after binutils/gcc/linux/g [...] discards 484d093ff53b 53: onsuccess: #790: 1: Success after binutils/gcc/linux/g [...] discards 43d5a48a1abc 52: onsuccess: #789: 1: Success after binutils/gcc/linux/g [...] discards 9518be25d42f 51: onsuccess: #788: 1: Success after binutils/gcc/linux/g [...] discards 5ce5f6c7bce8 50: onsuccess: #787: 1: Success after binutils/gcc/linux/g [...] discards b00646019ac1 49: onsuccess: #785: 1: Success after binutils: 12 commits discards b9e69b678516 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 6793e11f3f0c 47: onsuccess: #780: 1: Success after binutils/gcc/linux/g [...] discards e69768bf90ff 46: onsuccess: #779: 1: Success after binutils/gcc/linux/g [...] discards 97f422f4c212 45: onsuccess: #778: 1: Success after binutils/gcc/linux/g [...] discards f45cc979b9f5 44: onsuccess: #777: 1: Success after binutils/gcc/linux/g [...] discards 0affe18c2092 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/g [...] discards 286ba08eb581 42: onsuccess: #775: 1: Success after binutils/gcc/linux/g [...] discards 9fd137ae3e69 41: onsuccess: #774: 1: Success after binutils/gcc/linux/g [...] discards 3fc24a1ad737 40: onsuccess: #773: 1: Success after binutils/gcc/linux/g [...] discards 7208a885cb2e 39: onsuccess: #772: 1: Success after binutils/gcc/linux/g [...] discards ad983d01f651 38: onsuccess: #771: 1: Success after binutils/gcc/linux/g [...] discards 1e14b15f7f8e 37: onsuccess: #770: 1: Success after binutils/gcc/linux/g [...] discards 3598d8deef4e 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 [...] discards 0237956b63b5 35: onsuccess: #768: 1: Success after binutils/gcc/linux/g [...] new 21950d7bd1c3 35: onsuccess: #768: 1: Success after binutils/gcc/linux/g [...] new 6c3dceee5125 36: onsuccess: #769: 1: Success after binutils/gcc/gdb: 22 [...] new fb7ba709050f 37: onsuccess: #770: 1: Success after binutils/gcc/linux/g [...] new 6a5db62df24b 38: onsuccess: #771: 1: Success after binutils/gcc/linux/g [...] new 409ff4e3601a 39: onsuccess: #772: 1: Success after binutils/gcc/linux/g [...] new bdc9fb4a3bf7 40: onsuccess: #773: 1: Success after binutils/gcc/linux/g [...] new ba5420889b9f 41: onsuccess: #774: 1: Success after binutils/gcc/linux/g [...] new 4ba75cecb456 42: onsuccess: #775: 1: Success after binutils/gcc/linux/g [...] new 0a9686de4bf3 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/g [...] new 08c116273ca1 44: onsuccess: #777: 1: Success after binutils/gcc/linux/g [...] new 402fb358171c 45: onsuccess: #778: 1: Success after binutils/gcc/linux/g [...] new 86bcea113990 46: onsuccess: #779: 1: Success after binutils/gcc/linux/g [...] new 2adac321a2c0 47: onsuccess: #780: 1: Success after binutils/gcc/linux/g [...] new f15b0ddf492b 48: onsuccess: #782: 1: Success after binutils: 8 commits new cdabf653327b 49: onsuccess: #785: 1: Success after binutils: 12 commits new b8edd3a008b8 50: onsuccess: #787: 1: Success after binutils/gcc/linux/g [...] new 23195152e879 51: onsuccess: #788: 1: Success after binutils/gcc/linux/g [...] new 7f49cc1f8b07 52: onsuccess: #789: 1: Success after binutils/gcc/linux/g [...] new 892eb16b8ad8 53: onsuccess: #790: 1: Success after binutils/gcc/linux/g [...] new 4ddb3725d205 54: onsuccess: #791: 1: Success after binutils/gcc/linux/g [...] new ee0e25efeaa8 55: onsuccess: #792: 1: Success after binutils/gcc/linux/g [...] new db3c0d2d8859 56: onsuccess: #793: 1: Success after binutils/gcc/linux/g [...] new aa4891fbab39 57: onsuccess: #794: 1: Success after binutils/gcc/linux/g [...] new c68f5c3ae6d3 58: onsuccess: #795: 1: Success after binutils/gcc/linux/g [...] new ae39eb074545 59: onsuccess: #796: 1: Success after binutils/gcc/linux/g [...] new 6e91c01e6745 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/g [...] new 8f03bff3cdc0 61: onsuccess: #798: 1: Success after binutils/gcc/linux/g [...] new 4e010a4c8302 62: onsuccess: #799: 1: Success after binutils/gcc/linux/g [...] new 5cc028fc8c0a 63: onsuccess: #800: 1: Success after binutils/gcc/linux/g [...] new ea737a72bf64 64: onsuccess: #801: 1: Success after binutils/gcc/linux/g [...] new a0994fdd01ce 65: onsuccess: #802: 1: Success after binutils/gcc/linux/g [...] new e204d8950f72 66: onsuccess: #803: 1: Success after binutils/gcc/linux/g [...] new 49db19ae1f32 67: onsuccess: #804: 1: Success after binutils/gcc/linux/g [...] new a9a41b5c1d3a 68: onsuccess: #805: 1: Success after binutils/gcc/linux/g [...] new bd02c699c2c6 69: onsuccess: #806: 1: Success after binutils/gcc/linux/g [...] new 81afde358bba 70: onsuccess: #807: 1: Success after binutils/gcc/linux/g [...] new 0ae719379a1f 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/g [...] new 53a1712eb7d6 72: onsuccess: #809: 1: Success after binutils/gcc/linux/g [...] new a6ccff0629e7 73: onsuccess: #810: 1: Success after binutils/gcc/linux/g [...] new 80e13d6ae4a1 74: onsuccess: #811: 1: Success after binutils/gcc/linux/g [...] new c36f9d3fa1c0 75: onsuccess: #812: 1: Success after binutils/gcc/linux/g [...] new f4f14675babb 76: onsuccess: #813: 1: Success after binutils/gcc/linux/g [...] new d95533b0d897 77: onsuccess: #814: 1: Success after binutils/gcc/linux/g [...] new 06d39d87a193 78: onsuccess: #815: 1: Success after binutils/gcc/linux/g [...] new cca953d51af6 79: onsuccess: #816: 1: Success after binutils/gcc/linux/g [...] new 9f44a2f7d171 80: onsuccess: #817: 1: Success after binutils/gcc/linux/g [...] new ff39528a46fb 81: onsuccess: #818: 1: Success after binutils/gcc/linux/g [...] new cbc695fb943c 82: onsuccess: #819: 1: Success after binutils/gcc/linux/g [...] new c8761d894bd7 83: onsuccess: #820: 1: Success after binutils/gcc/linux/g [...] new deb692688bf1 84: onsuccess: #821: 1: Success after binutils/gcc/linux/g [...] new 1329f0df90f1 85: onsuccess: #822: 1: Success after binutils/gcc/linux/g [...] new 4c024cf639ee 86: onsuccess: #823: 1: Success after binutils/gcc/linux/g [...] new 009f0b5bc5bd 87: onsuccess: #824: 1: Success after binutils/gcc/linux/g [...] new e60a258ee397 88: onsuccess: #825: 1: Success after binutils/gcc/linux/g [...] new 0b9ed8be8c86 89: onsuccess: #826: 1: Success after binutils/gcc/linux/g [...] new a56bd16b0594 90: onsuccess: #827: 1: Success after binutils/gcc/linux/g [...] new c0aaa7acb93a 91: onsuccess: #828: 1: Success after binutils/gcc/linux/g [...] new 6f371a0b3ab5 92: onsuccess: #829: 1: Success after binutils/gcc/linux/g [...] new d1fd89573aef 93: onsuccess: #830: 1: Success after binutils/gcc/linux/g [...] new 2295a145e064 94: onsuccess: #832: 1: Success after binutils: 5 commits new 0c0d83c95764 95: onsuccess: #835: 1: Success after binutils: 3 commits new 6cb131b12932 96: onsuccess: #837: 1: Success after binutils/gcc/linux/g [...] new 210b79e6bf12 97: onsuccess: #838: 1: Success after binutils/gcc/linux/g [...] new 0aaba906f399 98: onsuccess: #839: 1: Success after binutils/gcc/linux/g [...] new b1af2a728b25 99: onsuccess: #840: 1: Success after binutils/gcc/linux/g [...] new 2239cdff724e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/ [...] new 685365b17a20 101: onsuccess: #842: 1: Success after binutils/gcc/linux/ [...] new b3d01322b95c 102: onsuccess: #843: 1: Success after binutils/gcc/linux/ [...] new 3cff428d6f4c 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 5 [...] new eebc04542584 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 6 [...] new 4d767328937c 105: onsuccess: #846: 1: Success after binutils/gcc/linux/ [...] new 8d76471cb625 106: onsuccess: #847: 1: Success after binutils/gcc/linux/ [...] new af3dd8c212a4 107: onsuccess: #849: 1: Success after binutils: 5 commits new c5024ed3bc04 108: onsuccess: #850: 1: Success after gcc: 2 commits new ab33270e1dd0 109: onsuccess: #852: 1: Success after binutils/gcc/linux/ [...] new 80a464e9e6d4 110: onsuccess: #853: 1: Success after binutils/gcc/linux/ [...] new 22351ffce710 111: onsuccess: #854: 1: Success after binutils/gcc/linux/ [...] new d94259804d22 112: onsuccess: #855: 1: Success after binutils/gcc/linux/ [...] new 646ffb5450be 113: onsuccess: #856: 1: Success after binutils/gcc/linux/ [...] new 12ea372f7af7 114: onsuccess: #857: 1: Success after binutils/gcc/linux/ [...] new 113421da8870 115: onsuccess: #858: 1: Success after binutils/gcc/linux/ [...] new 0483d68c6500 116: onsuccess: #859: 1: Success after binutils/gcc/linux/ [...] new 2a0ed6604dbb 117: onsuccess: #861: 1: Success after binutils: 18 commits new d087899ee440 118: onsuccess: #863: 1: Success after linux: 12 commits new 6a1d95fef59d 119: onsuccess: #864: 1: Success after binutils/gcc/linux/ [...] new 5241daf3186a 120: onsuccess: #865: 1: Success after binutils/gcc/linux/ [...] new e185a41fe106 121: onsuccess: #866: 1: Success after binutils/gcc/linux/ [...] new 85faa99a8ab1 122: onsuccess: #867: 1: Success after binutils/gcc/linux/ [...] new a82635fc5a4e 123: onsuccess: #868: 1: Success after binutils/gcc/linux/ [...] new 8a4f559ceb8a 124: onsuccess: #869: 1: Success after binutils/gcc/linux/ [...] new dbb15ba38b20 125: onsuccess: #871: 1: Success after binutils: 26 commits new 4e9a0b5840dd 126: onsuccess: #873: 1: Success after glibc: 2 commits new c8bc9aece550 127: onsuccess: #874: 1: Success after linux: 219 commits new 67c3444a385c 128: onsuccess: #876: 1: Success after binutils: 12 commits new e8fe6b5d5eb1 129: onsuccess: #878: 1: Success after linux: 3008 commits new 5e1abaed8da7 130: onsuccess: #879: 1: Success after binutils/gcc/linux/ [...] new 0b4f2731270b 131: onsuccess: #880: 1: Success after binutils/gcc/linux/ [...] new 5fb6a420fa1f 132: onsuccess: #881: 1: Success after binutils/gcc/linux/ [...] new 57777092c2bc 133: onsuccess: #882: 1: Success after binutils/gcc/linux/ [...] new f371bb21efed 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 1 [...] new 87ef2232e20b 135: onsuccess: #884: 1: Success after binutils/gcc/linux/ [...] new 4852c0a0fb34 136: onsuccess: #885: 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 (fa2721d047da) \ 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 1796 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 40084 -> 39872 bytes 04-build_abe-gcc/console.log.xz | Bin 216600 -> 215640 bytes 06-build_abe-linux/console.log.xz | Bin 8988 -> 8516 bytes 07-build_abe-glibc/console.log.xz | Bin 243548 -> 245640 bytes 08-build_abe-gdb/console.log.xz | Bin 39328 -> 39428 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3896 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2568 -> 3288 bytes 11-check_regression/console.log.xz | Bin 6768 -> 6788 bytes 11-check_regression/mail-body.txt | 27 - 11-check_regression/results.compare | 15 - 11-check_regression/results.compare2 | 68 +- 12-update_baseline/console.log | 62 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 3774856 -> 3761124 bytes sumfiles/g++.sum | 59 +- sumfiles/gcc.log.xz | Bin 3308548 -> 3311640 bytes sumfiles/gcc.sum | 4553 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1079996 -> 1078032 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2268 -> 2272 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233052 -> 233408 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2676 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 456572 -> 450176 bytes sumfiles/libstdc++.sum | 2 +- 38 files changed, 2424 insertions(+), 2455 deletions(-)