We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
#596
Run actions/upload-artifact@65d8626 With the provided path, there will be 1 file uploaded Starting artifact upload For more detailed logs during the artifact upload process, enable step-debugging: https://docs.github.com/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging#enabling-step-debug-logging Artifact name is valid! Create Artifact Container - Error is not retryable
Status Code: 400 Status Message: Bad Request Header Information: { "content-length": "268", "content-type": "application/json; charset=utf-8", "date": "Tue, 04 Feb 2025 21:06:55 GMT", "server": "Kestrel", "cache-control": "no-store,no-cache", "pragma": "no-cache", "strict-transport-security": "max-age=2592000", "x-tfs-processid": "b3090b1d-2168-447b-b64c-28fcc678be30", "activityid": "ac6f51e2-5723-4f45-aec5-164a6aeb79af", "x-tfs-session": "ac6f51e2-5723-4f45-aec5-164a6aeb79af", "x-vss-e2eid": "ac6f51e2-5723-4f45-aec5-164a6aeb79af", "x-vss-senderdeploymentid": "f7faf8cf-7ae4-3f62-0792-ce64b15bce23", "x-frame-options": "SAMEORIGIN" }
Error: Create Artifact Container failed: The artifact name pr-number is not valid. Request URL https://pipelinesghubeus[13](https://github.com/ethereum/ERCs/actions/runs/13144837457/job/36680455003?pr=596#step:8:14).actions.githubusercontent.com/KwdeLLYxPzmxPzptEBTyh4RflJKoOGXuLuonGoV8xLM9dfyTgy/_apis/pipelines/workflows/13[14](https://github.com/ethereum/ERCs/actions/runs/13144837457/job/36680455003?pr=596#step:8:15)4837457/artifacts?api-version=6.0-preview
suddently all the PRs have the above checking issues.
There were good before.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Pull Request
#596
What happened?
Begin Diagnostic HTTP information
Status Code: 400
Status Message: Bad Request
Header Information: {
"content-length": "268",
"content-type": "application/json; charset=utf-8",
"date": "Tue, 04 Feb 2025 21:06:55 GMT",
"server": "Kestrel",
"cache-control": "no-store,no-cache",
"pragma": "no-cache",
"strict-transport-security": "max-age=2592000",
"x-tfs-processid": "b3090b1d-2168-447b-b64c-28fcc678be30",
"activityid": "ac6f51e2-5723-4f45-aec5-164a6aeb79af",
"x-tfs-session": "ac6f51e2-5723-4f45-aec5-164a6aeb79af",
"x-vss-e2eid": "ac6f51e2-5723-4f45-aec5-164a6aeb79af",
"x-vss-senderdeploymentid": "f7faf8cf-7ae4-3f62-0792-ce64b15bce23",
"x-frame-options": "SAMEORIGIN"
}
End Diagnostic HTTP information
Begin Diagnostic HTTP information
Status Code: 400
Status Message: Bad Request
Header Information: {
"content-length": "268",
"content-type": "application/json; charset=utf-8",
"date": "Tue, 04 Feb 2025 21:06:55 GMT",
"server": "Kestrel",
"cache-control": "no-store,no-cache",
"pragma": "no-cache",
"strict-transport-security": "max-age=2592000",
"x-tfs-processid": "b3090b1d-2168-447b-b64c-28fcc678be30",
"activityid": "ac6f51e2-5723-4f45-aec5-164a6aeb79af",
"x-tfs-session": "ac6f51e2-5723-4f45-aec5-164a6aeb79af",
"x-vss-e2eid": "ac6f51e2-5723-4f45-aec5-164a6aeb79af",
"x-vss-senderdeploymentid": "f7faf8cf-7ae4-3f62-0792-ce64b15bce23",
"x-frame-options": "SAMEORIGIN"
}
End Diagnostic HTTP information
Error: Create Artifact Container failed: The artifact name pr-number is not valid. Request URL https://pipelinesghubeus[13](https://github.com/ethereum/ERCs/actions/runs/13144837457/job/36680455003?pr=596#step:8:14).actions.githubusercontent.com/KwdeLLYxPzmxPzptEBTyh4RflJKoOGXuLuonGoV8xLM9dfyTgy/_apis/pipelines/workflows/13[14](https://github.com/ethereum/ERCs/actions/runs/13144837457/job/36680455003?pr=596#step:8:15)4837457/artifacts?api-version=6.0-preview
suddently all the PRs have the above checking issues.
There were good before.
Relevant log output
The text was updated successfully, but these errors were encountered: