when you run in the IDEBURG mode, you get an output with this as a n error message.
Error: No project file found! On 3/21/16, marko kiiskila <[email protected]> wrote: > Hi, > > can you run it with -lDEBUG to see how it is failing? > > newt -lDEBUG test libs/json > > > >> On Mar 20, 2016, at 9:24 PM, Nges B <[email protected]> wrote: >> >> I think there is a problem with current libs/json >> I just cloned and still have the test failure. >> >> On 3/21/16, Nges B <[email protected]> wrote: >>> Ok let me clone again might be there is a problem with >>> incubetor-mynewt-core. >>> >>> >>> On 3/21/16, Nges B <[email protected]> wrote: >>>> when I run mine I have a failure. >>>> >>>> Compiling util_test.c >>>> Archiving util.a >>>> Linking test_json >>>> Executing test: >>>> /home/nges/incubator-mynewt-core/bin/unittest/libs/json/test_json >>>> Error: Test failure(s): >>>> Passed tests: [] >>>> Failed tests: [libs/json] >>>> >>>> >>>> On 3/21/16, Sterling Hughes <[email protected]> wrote: >>>>> Hi Nges, >>>>> >>>>> Do you have a Github fork, and can you check in what's failing for >>>>> you? >>>>> It might be easiest to check what you've got. >>>>> >>>>> When I run it on origin/develop, I get: >>>>> >>>>> $ newt test libs/json >>>>> Testing package libs/json >>>>> Compiling json_decode.c >>>>> Compiling json_encode.c >>>>> Compiling test_json.c >>>>> Compiling test_json_simple.c >>>>> Archiving json.a >>>>> Compiling hal_bsp.c >>>>> Compiling os_bsp.c >>>>> Compiling sbrk.c >>>>> Archiving native.a >>>>> Compiling hal_cputime.c >>>>> Compiling hal_flash.c >>>>> Compiling hal_gpio.c >>>>> Compiling hal_system.c >>>>> Compiling hal_uart.c >>>>> Archiving native.a >>>>> Compiling os.c >>>>> Compiling os_callout.c >>>>> Compiling os_eventq.c >>>>> Compiling os_heap.c >>>>> Compiling os_mbuf.c >>>>> Compiling os_mempool.c >>>>> Compiling os_mutex.c >>>>> Compiling os_sanity.c >>>>> Compiling os_sched.c >>>>> Compiling os_sem.c >>>>> Compiling os_task.c >>>>> Compiling os_time.c >>>>> Compiling os_arch_sim.c >>>>> Compiling os_fault.c >>>>> Assembling os_arch_stack_frame.s >>>>> Compiling mbuf_test.c >>>>> Compiling mempool_test.c >>>>> Compiling mutex_test.c >>>>> Compiling os_test.c >>>>> Compiling sem_test.c >>>>> Compiling os_test_arch_sim.c >>>>> Archiving os.a >>>>> Compiling case.c >>>>> Compiling suite.c >>>>> Compiling testutil.c >>>>> Compiling testutil_arch_sim.c >>>>> Archiving testutil.a >>>>> Compiling flash_map.c >>>>> Compiling hal_flash.c >>>>> Compiling flash_map_test.c >>>>> Archiving hal.a >>>>> Compiling base64.c >>>>> Compiling cbmem.c >>>>> Compiling datetime.c >>>>> Compiling tpq.c >>>>> Compiling cbmem_test.c >>>>> Compiling util_test.c >>>>> Archiving util.a >>>>> Linking test_json >>>>> Executing test: >>>>> /Users/sterling/dev/core/bin/unittest/libs/json/test_json >>>>> Passed tests: [libs/json] >>>>> All tests passed >>>>> $ >>>>> >>>>> Cheers, >>>>> Sterling >>>>> >>>>> On 3/20/16 8:22 PM, Nges B wrote: >>>>>> Hi, >>>>>> I have created a test project but when I test the code, the test >>>>>> libs/json fails I do not understand. >>>>>> In the Documentation , it is all test cases passed. >>>>>> >>>>>> On 3/21/16, Sterling Hughes <[email protected]> wrote: >>>>>>> Outstanding!!! >>>>>>> That's great news. >>>>>>> >>>>>>> Sterling >>>>>>> >>>>>>> On 3/20/16 6:57 PM, Nges B wrote: >>>>>>>> thanks very much. I rate some work and I did >>>>>>>> >>>>>>>> export GOPATH=$HOME/dev/go >>>>>>>> >>>>>>>> which set the gopath to dev/go directory and I have succeeded to >>>>>>>> compile the lasted version of newt 0.8.0-b2 >>>>>>>> >>>>>>>> On 3/21/16, [email protected] <[email protected]> wrote: >>>>>>>>> What is the error message you get when you try to run it? >>>>>>>>> >>>>>>>>> On 3/20/16, 3:33 PM, "Nges B" <[email protected]> wrote: >>>>>>>>> >>>>>>>>>> Thanks very much. >>>>>>>>>> But I still do not have the error message . >>>>>>>>>> >>>>>>>>>> On 3/20/16, [email protected] <[email protected]> wrote: >>>>>>>>>>> export GOROOT= >>>>>>>>>>> >>>>>>>>>>> On 3/20/16, 3:30 PM, "Nges B" <[email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> so how can I unset GOROOT? >>>>>>>>>>>> >>>>>>>>>>>> On 3/20/16, [email protected] <[email protected]> wrote: >>>>>>>>>>>>> When I installed Go 1.6, I found that I set GOPATH to >>>>>>>>>>>>> $HOME/dev/go >>>>>>>>>>>>> and >>>>>>>>>>>>> $GOROOT was unset. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On 3/20/16, 3:14 PM, "Nges B" <[email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>> Please how do I install go1.6 on my machine to be able to >>>>>>>>>>>>>> install >>>>>>>>>>>>>> newt. >>>>>>>>>>>>>> I have tried >>>>>>>>>>>>>> sudo tar -C /usr/local -xzf go1.6.linux-amd64.tar.gz >>>>>>>>>>>>>> PATH=$PATH:/usr/local/go/bin >>>>>>>>>>>>>> export GOROOT=$HOME/dev/go >>>>>>>>>>>>>> export PATH=$PATH:$GOROOT/bin >>>>>>>>>>>>>> but gets and it seems as if go is not installed on my system >>>>>>>>>>>>>> properly. >>>>>>>>>>>>>> >>>>>>>>>>>>>> please can someone help. >>>>>>>>>>>>>> Thanks in advance >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> "it is good to dream and work for the dreams than not to dream" >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> "it is good to dream and work for the dreams than not to dream" >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> "it is good to dream and work for the dreams than not to dream" >>>> >>> >>> >>> -- >>> "it is good to dream and work for the dreams than not to dream" >>> >> >> >> -- >> "it is good to dream and work for the dreams than not to dream" > > -- "it is good to dream and work for the dreams than not to dream"
