-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to primary Google Account email address #8097
Conversation
Build error isn't caused by this change, at least. I've opened an issue on pest to try to diagnose the build failure; it looks like it likely has to do with the bootstrap process building/running not under asan but thinking it is; we probably need to clear some env variables before running |
As with google#8090 google#8097 I cannot access the pages with oss-fuzz bug reports (e.g. links in pest-parser/pest#674). I am one of maintainers (you can verify my address by checking the recent pest repository git log entries).
As with #8090 #8097 I cannot access the pages with oss-fuzz bug reports (e.g. links in pest-parser/pest#674). I am one of maintainers (you can verify my address by checking the recent pest repository git log entries).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
As with google#8090 google#8097 I cannot access the pages with oss-fuzz bug reports (e.g. links in pest-parser/pest#674). I am one of maintainers (you can verify my address by checking the recent pest repository git log entries).
As with google#8090 google#8097 I cannot access the pages with oss-fuzz bug reports (e.g. links in pest-parser/pest#674). I am one of maintainers (you can verify my address by checking the recent pest repository git log entries).
as with #8090, #8099; closes #8096
(See my profile to confirm that this is me.)
A proper way for
auto_ccs
to log in and see the chromium bug would still be useful, but this at least gets me access.