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_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts.
discards eb2af62a79 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 363e9ad5a8 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 536c06cadf 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards b265063fa3 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 862c0b4688 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 64adfd259e 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1c8f97cc9b 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2cb08392db 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 1a2533a1cb 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 937720316e 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards aba8afb024 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 5690376e31 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 7d618861af 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 704b3890bf 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards d2aa6b752d 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards f034dca806 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 78dc09996d 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 8b07fdf19c 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards ff525612ce 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ee7bef93f0 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards e0b3f751c8 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 3fb04339c2 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 17ac02c96c 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 73e69265a9 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 0d282af3f9 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards a3e08bd698 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 419c8ff7c1 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards b7b41fabe9 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards b8dcafa8cb 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 3f7229adc6 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 5b94e4c1c3 121: force: #26: : Failure after baseline build: no new commits discards 205a137efc 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards ce110b62c4 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards c05716440c 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 78f7d80232 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 2b77b56a3f 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards a5622c7e77 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards bd391003ea 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards a8857793d2 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 29c6274c70 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards b3c0a3d06d 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 1871a2614f 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 4acf678b87 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 0327697aab 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 02f7440d8c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 10c97a0053 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 9c62ab051b 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards a21f1fb22d 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 9845c7beea 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 11300c049f 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 2cba4c44d0 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 6544135115 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 613e584013 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 29ee77aa9e 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards eb812b6947 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 3930667149 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 9bcfe4af27 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards 4e0b6fa15f 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 1e944ca39f 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards b8df005a53 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards cd2352536f 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards e409838e6f 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 99a662366d 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards a6014ee4d9 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards b50466c1f0 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 45a2c5389e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards e17089f884 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards c0e450cc20 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 4eb21b16a4 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 0857433a37 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 42556f46c9 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 84add8c60e 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 07ca128d7d 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards 3aa5ea97b0 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards d29ca8f73e 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards c99343a679 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards 4b3e71289d 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards eac807e603 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards e419d2bc2f 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 7cd20ae57f 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 615cee8f29 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 016580871a 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 11d111ed98 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards bb47a22e68 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards a7417c0a7f 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 2f4e7fb4e1 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 038038b1aa 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 0068c9ea52 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 37db5e928b 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 1c51b21097 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards f432875b60 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 32bbc74cfc 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards a360683386 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 10d0035174 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 0c171b51c1 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards c4a4e67f85 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 3eb099da4d 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 646905772a 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards d2345f5ec3 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 4742a4c2d3 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards 3f57f2c195 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 875bc611f0 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 59d633c704 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 2d9235a547 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 690dc1d1fe 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 7bc48d4eea 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 56a0df4b06 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 685ee4f9fc 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 6c2bf1cf1a 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new 35950d4142 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 9cb19b107c 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 994065f2a4 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 831bccde04 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 7d1a67dec8 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new ee433910f9 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 8707de5836 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new ae3dffd321 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 7bfb2153ea 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 2b802ec7f0 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 10279e7320 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 185fe47a16 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new ddc17664fe 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new c7bc104faf 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new f490ccd566 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new f469e51b43 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new a9e9ccde09 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new f1ab331e13 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new e14db4397a 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new e47c868621 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new d90d07bb01 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 58fb98d871 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new e396ac67fb 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new c6240ad85d 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new c618bca985 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 5822934a27 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new c83c0e59c3 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new d1bd9f0a57 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new a1f7ad05b1 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 64c0656176 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 7d15a50119 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 8b65826437 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new 8e8ab780c6 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new a9ab99815e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 5a526f1633 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new c7d222a0bf 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 16af8f6cc2 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 1765766364 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 61460d4ab8 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new dea4206363 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new b697b015c3 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 51aed87cf3 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 042f8b9c1a 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new b7df53fbe1 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new b784d2e6ec 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new e9b794f41f 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new fdf94106c4 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 5cfe658005 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 447ac86c46 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new b73e3a342b 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 6e4cdc3cb2 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 5cb98a5362 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 8393e368a3 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 12aea23d8e 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 528aec8085 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 57d65983da 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 6c6c89d87d 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 4b67c9bae1 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new ec3f53ae7b 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 768cc14f48 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 12e9bba4e7 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 96c2b36ec3 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new df509aa48b 121: force: #26: : Failure after baseline build: no new commits new 5f40ad0a97 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new eddb521e01 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new cd1245b365 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 053382837b 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new e008777d6b 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 96663104ea 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 53a990eabe 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 5d5e90baf3 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new c1e2e832db 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 57862af647 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new ca64634a0e 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 681a6f6734 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new bf5a785fb6 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new dc38d74aa9 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 8f1c162df4 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 104407fbb1 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 4c17fad510 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 1078d9c839 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 3186da9993 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new afce4166f6 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 579fb4df8a 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new bcffa0b6d5 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 618d9faab4 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 703735ef8f 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 43e366db7b 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d5edcc19ff 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 77c6af12b3 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new ed587d1235 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 778216b04e 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 7fe7bd0f29 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5f6e845e0a 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...]
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 (eb2af62a79) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...]
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 2052 -> 2248 bytes 02-prepare_abe/console.log.xz | Bin 2456 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 49804 -> 48992 bytes 04-build_abe-gcc/console.log.xz | Bin 236752 -> 235144 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8284 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 232736 -> 232596 bytes 08-build_abe-gdb/console.log.xz | Bin 48308 -> 47244 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3804 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4136 -> 3216 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 548 -> 1276 bytes 11-check_regression/results.compare | 7 ++++++ 11-check_regression/results.compare2 | 42 ++++++++++++++++++++++++++++++++ 12-update_baseline/console.log | 44 +++++++++++++++++----------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 7 ++++++ manifest.sh | 34 +++++++++++++------------- sumfiles/gdb.log.xz | Bin 14216 -> 14232 bytes sumfiles/gdb.sum | 4 ++-- 25 files changed, 104 insertions(+), 48 deletions(-) create mode 100644 11-check_regression/results.compare create mode 100644 11-check_regression/results.compare2 create mode 100644 mail/results.compare