Skip to content

Update metrics-regress.yml#909

Draft
pradheepkaliraj wants to merge 1 commit intomasterfrom
pradheepkaliraj-patch-1
Draft

Update metrics-regress.yml#909
pradheepkaliraj wants to merge 1 commit intomasterfrom
pradheepkaliraj-patch-1

Conversation

@pradheepkaliraj
Copy link
Copy Markdown
Collaborator

Fix for "Please update the following actions to use Node.js 16: actions/checkout, actions/checkout"

Fix for "Please update the following actions to use Node.js 16: actions/checkout, actions/checkout"
@MikeOpenHWGroup
Copy link
Copy Markdown

Are Metrics CI regressions still running?

@pradheepkaliraj
Copy link
Copy Markdown
Collaborator Author

No, there is an issue with metric_regress.py when making a http request.
It fails with the following error socket.gaierror: [Errno -3] Temporary failure in name resolution.
https://github.com/google/riscv-dv/blob/1246c391cbbc3e161178dcb1aa88f34c84d123c2/scripts/metrics-regress.py

I am looking into this.

@MikeOpenHWGroup
Copy link
Copy Markdown

It is my understanding that Metrics has depreciated their cloud-based regression platform.

@pradheepkaliraj
Copy link
Copy Markdown
Collaborator Author

That makes sense. The server doesn't exist anymore. Should I revert this action then, so people don't get a regression failure mail, every time they commit a change?

@MikeOpenHWGroup
Copy link
Copy Markdown

Yes, that makes sense. Metrics has changed their product offering and it is not clear if the regression service will be offered in the near to mid-term future.

@MikeOpenHWGroup
Copy link
Copy Markdown

Hi @pradheepkaliraj, this PR has stalled out. As we discussed, please revert this action so people don't get a regression failure mail every time they commit a change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants