Skip to content
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

Resistor Color tests fail once submitted #1448

Closed
mikeHag opened this issue Feb 12, 2022 · 0 comments · Fixed by #1485
Closed

Resistor Color tests fail once submitted #1448

mikeHag opened this issue Feb 12, 2022 · 0 comments · Fixed by #1485

Comments

@mikeHag
Copy link

mikeHag commented Feb 12, 2022

This may be a duplicate of #1411, but the errors I get do not indicate a timeout.

The test pass on my local machine but once submitted, I always get an error related to the the version of proc-macro2.

I'll provide three examples. I have tried the test on the exercism site multiple times. #1411 implies that it will eventually work but that has not been my experience.

When I had no dependency for proc-macro2:
error: failed to select a version for the requirement proc-macro2 = "^1.0.4"
candidate versions found which didn't match: 1.0.33
location searched: /opt/test-runner/local-registry index (which is replacing registry crates-io)

When I used the dependency proc-macro2 = "1.0.4":
error: failed to select a version for the requirement proc-macro2 = "^1.0.4"
candidate versions found which didn't match: 1.0.33

When I used the dependency proc-macro2 = "1.0.33":
error: failed to select a version for the requirement proc-macro2 = "^1.0.33"
candidate versions found which didn't match: 1.0.33

@coriolinus coriolinus linked a pull request May 13, 2022 that will close this issue
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 a pull request may close this issue.

1 participant