You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Rainer Jung <ra...@kippdata.de> on 2022/04/20 21:52:00 UTC
git push ERROR wrt. CI
I currently see ERROR messages when doing git push. The push itself
seems to work and triggers eg. travis, but the error seems related with
CI. Example:
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 2 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 349 bytes | 43.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: To github:apache/tomcat.git
remote: 7c0dd42ac4..9c8c76378e
9c8c76378ed0d48ecdcb586d9a0a2cd83820da78 -> main
remote: Syncing refs/heads/main...
remote: Sending notification emails to: ['"dev@tomcat.apache.org"
<de...@tomcat.apache.org>']
and then the error:
remote: git_buildbot: ERROR: Could not connect to ci2.apache.org:9989:
Unicode-objects must be encoded before hashing
To https://gitbox.apache.org/repos/asf/tomcat
7c0dd42ac4..9c8c76378e main -> main
It happened for all branches.
Does anyone know whether that's a problem and what needs to be done?
Best regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: git push ERROR wrt. CI
Posted by Rainer Jung <ra...@kippdata.de>.
Am 21.04.2022 um 09:56 schrieb Mark Thomas:
> On 20/04/2022 22:52, Rainer Jung wrote:
>>
>> I currently see ERROR messages when doing git push. The push itself
>> seems to work and triggers eg. travis, but the error seems related
>> with CI. Example:
>>
>> Enumerating objects: 5, done.
>> Counting objects: 100% (5/5), done.
>> Delta compression using up to 2 threads
>> Compressing objects: 100% (3/3), done.
>> Writing objects: 100% (3/3), 349 bytes | 43.00 KiB/s, done.
>> Total 3 (delta 2), reused 0 (delta 0)
>> remote: To github:apache/tomcat.git
>> remote: 7c0dd42ac4..9c8c76378e
>> 9c8c76378ed0d48ecdcb586d9a0a2cd83820da78 -> main
>> remote: Syncing refs/heads/main...
>> remote: Sending notification emails to: ['"dev@tomcat.apache.org"
>> <de...@tomcat.apache.org>']
>>
>> and then the error:
>>
>> remote: git_buildbot: ERROR: Could not connect to ci2.apache.org:9989:
>> Unicode-objects must be encoded before hashing
>>
>> To https://gitbox.apache.org/repos/asf/tomcat
>> 7c0dd42ac4..9c8c76378e main -> main
>>
>>
>> It happened for all branches.
>>
>> Does anyone know whether that's a problem and what needs to be done?
>
> It looks like we haven't had any CI builds triggered by commits for
> several weeks. I suspect the error you see above is the cause.
>
> My recommendation is that you open an INFRA ticket to report the issue.
Thanks Mark, done: https://issues.apache.org/jira/browse/INFRA-23180
Best regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: git push ERROR wrt. CI
Posted by Mark Thomas <ma...@apache.org>.
On 20/04/2022 22:52, Rainer Jung wrote:
>
> I currently see ERROR messages when doing git push. The push itself
> seems to work and triggers eg. travis, but the error seems related with
> CI. Example:
>
> Enumerating objects: 5, done.
> Counting objects: 100% (5/5), done.
> Delta compression using up to 2 threads
> Compressing objects: 100% (3/3), done.
> Writing objects: 100% (3/3), 349 bytes | 43.00 KiB/s, done.
> Total 3 (delta 2), reused 0 (delta 0)
> remote: To github:apache/tomcat.git
> remote: 7c0dd42ac4..9c8c76378e
> 9c8c76378ed0d48ecdcb586d9a0a2cd83820da78 -> main
> remote: Syncing refs/heads/main...
> remote: Sending notification emails to: ['"dev@tomcat.apache.org"
> <de...@tomcat.apache.org>']
>
> and then the error:
>
> remote: git_buildbot: ERROR: Could not connect to ci2.apache.org:9989:
> Unicode-objects must be encoded before hashing
>
> To https://gitbox.apache.org/repos/asf/tomcat
> 7c0dd42ac4..9c8c76378e main -> main
>
>
> It happened for all branches.
>
> Does anyone know whether that's a problem and what needs to be done?
It looks like we haven't had any CI builds triggered by commits for
several weeks. I suspect the error you see above is the cause.
My recommendation is that you open an INFRA ticket to report the issue.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org