https://pantsbuild.org/ logo
Join Slack
Powered by
Has anyone seen this error before: (this is on osx...
# general
p
Has anyone seen this error before: (this is on osx)
Copy code
11:36:26.78 [INFO] Completed: Run setuptools_scm for libs:_version
11:36:26.79 [ERROR] 1 Exception encountered:

Engine traceback:
  in `package` goal

ProcessExecutionFailure: Process 'Run setuptools_scm for libs:_version' failed with exit code 1.
stdout:

stderr:
('ERROR: no version found for', Namespace(root='/Users/ben/espresso', config='pyproject.synthetic.toml', strip_dev=False, command=None))
h
Hmm, sounds like you have a 
vcs_version
target in your repo?
That should be the only thing that triggers setuptools_scm
p
yes, it looks like we do
h
ok, so this has all worked in the past then?
Best thing to do is run with 
--keep-sandboxes=on_failure
and look inside that sandbox
p
it all actually works currently on my machine, but does not on this specific machine
h
Hmmmm
And your machine (where it does work) is also osx?
Are they both the same platform? (ARM or X86)
p
no, my machine is linux x64 vs apple arm where it fails
Though I think I had it working on a different macbook
I will double check that when I'm in the office
I feel like it is probably some idiosyncratic setup on this specific macbook that causes it to fail, I just have no idea what that could be
h
Looking inside the failed sandbox is a good way to debug this
You can run 
__run.sh
in the sandbox and see what happens, maybe there are flags you can add to whatever that command is to generate more debug info
p
makes sense
I'll probably leave it alone for now though if it's not obvious what's wrong, it's the CEO's macbook, so he can probably do without needing to deploy to prod and get back to some sales calls 😂
😆 1
5 Views
Open in Slack
PreviousNext
Powered by