Closed simonadamprog closed 1 year ago
Apologies for the delay replying!
Yes, you're most likely correct that it's an issue with Mac M1 chips - I think it's the same issue as https://github.com/microsoft/qsharp-compiler/issues/1362, though in Jupyter Notebooks it manifests slightly differently. You could try to set up the Katas as Q# projects and then use the workaround described in that issue to use an older version of the simulator that doesn't have this problem. This wouldn't work for Jupyter Notebooks, though, as the %kata
magic uses CounterSimulator
which, in turn, uses QuantumSimulator
which exhibits this issue. I don't think there's an easy way to fix this in the Katas, since they have to rely on the simulator for the tests.
I'm trying to go through the readme part for running QuantumKatas locally. I rebased my work branch recently with upstream. I'm running the:
And the command line is stuck at this point for half an hour now:
I have an M1 proc. with .NET 6.0 (for this architecture) installed. I also tried to run "dotnet test", but I'm getting the issue described in: https://github.com/microsoft/qsharp-compiler/issues/1273
Can it be an issue also with this docker build that there is a mismatch between architectures?
UPDATE: For second try it gave me this error:
Yeah I guess it is a cpu architecture issue.