3 ms·
Getting this error while running ./make.sh: Hello, world! Hello, world! * Running test: ./out/example_loader Traceback (most recent call last):
by gnufied 11y ago
Getting this error while running ./make.sh:
Hello, world!
Hello, world!
* Running test: ./out/example_loader
Traceback (most recent call last):
File "tests/run_tests.py", line 57, in <module>
Main()
File "tests/run_tests.py", line 40, in Main
RunTest(['./out/example_loader'], -1, use_elf_loader=False)
File "tests/run_tests.py", line 34, in RunTest
subprocess.check_call(['./out/restore'])
File "/usr/lib64/python2.7/subprocess.py", line 540, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['./out/restore']' returned non-zero exit status -11
Interestingly the project has Github issues disabled.
- gboudrias 11y ago> Interestingly the project has Github issues disabled. This is pretty weird. Certainly goes against the spirit of free software in my book. It's not like they have to answer any issues. (Oh right it's Google. Well that explains that.)
- patrickaljord 11y agoActually there is nothing in the definition of free software that requires a bug tracker, even by gnu.org and rms standards and they're pretty high.
- teddyh 11y agogboudrias said “spirit”, not “definition”.
- noja 11y agoHaving Issues enabled sets the expectation that they are going to do something about your issue.