-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Hey Team, we are using the Code Coverage action. Below is how it looks.
name: code-coverage
on:
push:
branches: [main]
pull_request:
branches: [main]
permissions:
contents: read
statuses: write # CodeAnt sets commit statuses for gating
jobs:
coverage:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version: '1.24.x'
- name: Run tests with coverage (Go)
run: |
chmod +x coverage.sh
./coverage.sh
# CodeAnt’s docs suggest converting Go’s profile to XML before upload
- name: Convert Go coverage to Cobertura XML
run: |
go install github.com/axw/gocov/gocov@latest
go install github.com/AlekSi/gocov-xml@latest
gocov convert coverage.out | gocov-xml > coverage.xml
- name: Upload coverage to CodeAnt AI
uses: CodeAnt-AI/[email protected]
with:
access_token: ${{ secrets.ACCESS_TOKEN }}
coverage_file: coverage.xml
platform: github
api_base: 'https://api.codeant.ai'
base_url: 'https://github.com'
it was working previously, but somehow we are getting below error now:
Requesting presigned URLs...
Presigned URLs received.
Uploading coverage.xml
Completing coverage upload...
Error: Request failed with HTTP 504
Result: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
Response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>504 Gateway Timeout ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront) HTTP3 Server
Request ID: HFQjc9_rq-NsgH3y26tZigYO0P_DlnEdDTiCGzx5MsQzdatPBRxLag==
</PRE>
<ADDRESS>
</ADDRESS>
</BODY></HTML>
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>504 Gateway Timeout ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront) HTTP3 Server
Request ID: HFQjc9_rq-NsgH3y26tZigYO0P_DlnEdDTiCGzx5MsQzdatPBRxLag==
</PRE>
<ADDRESS>
</ADDRESS>
</BODY></HTML>
Although coverage is reaching to codeant, but my pipeline is failing due to this.
Metadata
Metadata
Assignees
Labels
No labels