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

Relative imports don't always work in jobTree #10

Open
dentearl opened this issue Jan 10, 2013 · 1 comment
Open

Relative imports don't always work in jobTree #10

dentearl opened this issue Jan 10, 2013 · 1 comment

Comments

@dentearl
Copy link
Collaborator

Per our conversation, jobTree sometimes loses track of where imports are coming from.

Reporting file: /hive/users/dearl/alignathon/testPSAR/jobTree_flies_reg2_swarm/jobs/tmp_IqnDTgr8uv/tmp_AzbE0HYFWt/tmp_70td82ax1K/log.txt
log.txt:        Parsed arguments and set up logging
log.txt:        Traceback (most recent call last):
log.txt:          File "/cluster/home/dearl/sonTrace/jobTree/bin/jobTreeSlave", line 206, in main
log.txt:            loadStack(command).execute(job=job, stats=stats,
log.txt:          File "/cluster/home/dearl/sonTrace/jobTree/bin/jobTreeSlave", line 53, in loadStack
log.txt:            _temp = __import__(moduleName, globals(), locals(), [className], -1)
log.txt:        ImportError: No module named batchPsar
log.txt:        Exiting the slave because of a failed job on host kkr18u44.local
log.txt:        Finished running the chain of jobs on this node, we ran for a total of 5.177906 seconds

Requires explicit setting of PYTHONPATH when running on swarm, when running on kolossus simply running from the same directory as the script is sufficient.

@dentearl
Copy link
Collaborator Author

Bump.

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

No branches or pull requests

1 participant