On 11/25/20 2:58 AM, H.J. Lu via Gcc wrote:
On Tue, Nov 24, 2020 at 5:19 PM Joseph Myers <jos...@codesourcery.com> wrote:
On Wed, 25 Nov 2020, (Cron Daemon) via Gccadmin wrote:
=== Working on: master ===
branch pulled and checked out
61 revisions since last Daily bump
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 100, in
update_current_branch
% (commit.hexsha, head.hexsha))
File "/tmp/tmp.yGFjw60tQz/gcc-changelog/git_repository.py", line 76, in
parse_git_revisions
commit_to_info_hook=commit_to_info)
File "/tmp/tmp.yGFjw60tQz/gcc-changelog/git_commit.py", line 281, in __init__
self.info = self.commit_to_info_hook(self.revert_commit)
File "/tmp/tmp.yGFjw60tQz/gcc-changelog/git_repository.py", line 37, in
commit_to_info
c = repo.commit(commit)
File "/home/gccadmin/.local/lib/python3.6/site-packages/git/repo/base.py",
line 480, in commit
return self.rev_parse(str(rev) + "^0")
File "/home/gccadmin/.local/lib/python3.6/site-packages/git/repo/fun.py",
line 213, in rev_parse
obj = name_to_object(repo, rev[:start])
File "/home/gccadmin/.local/lib/python3.6/site-packages/git/repo/fun.py",
line 147, in name_to_object
raise BadName(name)
gitdb.exc.BadName: Ref 'c4fa3728ab4f78984a549894e0e8c4d6a253e540,' did not
resolve to an object
I don't know where that comma after the commit id came from, but something
appears to have broken the update_version_git cron job.
Could it be
commit ce2d9549f2b2bcb70a1a6f8f4e776e1ed427546b
Author: Ulrich Weigand <ulrich.weig...@de.ibm.com>
Date: Tue Nov 24 19:30:01 2020 +0100
Revert: "Fix -ffast-math flags handling inconsistencies"
This reverts commit c4fa3728ab4f78984a549894e0e8c4d6a253e540,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
which caused a regression in the default for flag_excess_precision.
Hello.
I fixed that in d3e763efcb85d2b5967aeb3178567e435e796420 and Jakub will run the
cron job
manually.
Thanks for heads up.
Martin
