On Mon, Nov 02, 2020 at 08:14:22PM +0100, Rainer Orth wrote:
> I noticed that gcc/DATESTAMP isn't updated any longer after this
> Friday. I doubt this is intentional...
=== Working on: master ===
branch pulled and checked out
74 revisions since last Daily bump
writing to ./libstdc++-v3/ChangeLog
writing to ./gcc/ChangeLog
writing to ./gcc/testsuite/ChangeLog
writing to ./gcc/testsuite/ChangeLog
writing to ./gcc/cp/ChangeLog
writing to ./gcc/testsuite/ChangeLog
writing to ./gcc/ChangeLog
writing to ./gcc/testsuite/ChangeLog
writing to ./gcc/ChangeLog
writing to ./libgcc/ChangeLog
writing to ./gcc/ChangeLog
writing to ./gcc/ChangeLog
writing to ./gcc/testsuite/ChangeLog
empty group "()" found:" * tree-vect-slp.c (): Update backedges in
single-node cycles."
Traceback (most recent call last):
File "../gcc-changelog/git_update_version.py", line 143, in <module>
update_current_branch()
File "../gcc-changelog/git_update_version.py", line 103, in
update_current_branch
not args.dry_mode)
File "../gcc-changelog/git_update_version.py", line 39, in
prepend_to_changelog_files
raise AssertionError()
AssertionError
That's the Richard's commit that slipped through the verification, but
upsets ChangeLog generation.
Jakub
