Hi Austin,

you might need to install opencog before running the unit tests.

Nil

On 3/19/19 12:52 PM, Austin wrote:
Hello people!

Hope you are doing well. Since the last update, With cogutil and Atomspace building fine. some of the make tests for the opencog directory have failed on my end. Even though it seems to make ok. Please find attached a screenshot of these errors.

Also for a better work process; I'm trying to figure out how to work with docker. I would like to use opencog's atomspace in production through docker. However in building opencog with "docker-compose run --service-ports dev". There seems to be no module called "opencog.atomspace" in this dev docker container. Does atomspace exist as a different container ? If not, what changes may need to be made to make use of atomspace in the opencog docker environment ?

Thank you in advance :)

Austin

On Fri, Mar 15, 2019 at 12:32 PM Vitaly Bogdanov <[email protected] <mailto:[email protected]>> wrote:

    ParallelUTest issue should be fixed in latest master, please see
    https://github.com/opencog/atomspace/issues/2127

    On Friday, March 15, 2019 at 1:39:12 PM UTC+3, Austin wrote:

        Hi Vitaly

        Thank you for your reply! Yes indeed, I do have enough free
        memory. I have been able to build the atomspace by running make -j4.
        I understand without the number, it spawns a process for each
        core I have;  so it builds with only test 16 - ParallelUTest
        failing (SEGFAULT).
        However, I'll try the docker image if it makes things easier for
        regular updating and rebuilding of the libraries. Thanks again!

        Best,
        Austin



        On Wed, Mar 13, 2019 at 4:06 PM Vitaly Bogdanov
        <[email protected]> wrote:

            Hi Austin,

            My machine has 16 Gib of RAM, 5 of them are occupied by
            operating system almost constantly. At least it is enough to
            build opencog. I have just make a test and I didn't see more
            than 2 GiB were used during build. Have you tried executing
            "free" command to see how much of free memory do you have?

            Best regards,
               Vitaly


            On Tuesday, March 12, 2019 at 7:54:06 PM UTC+3, Austin wrote:

                Hi,

                After reinstalling and recompiling for the new updates.
                In running make for the atomspace. I get errors such as
                virtual memory exhausted: Cannot allocate memory.Find
                attached the error images in detail.

                Please what could cause this; The AWS EC2 instance type
                used is t3.large. Also, I am wondering if any specific
                recommendations of memory size required to run all of
                opencog efficiently ?

                Greatly appreciate any help provided.
                Thank you!

-- You received this message because you are subscribed to the
            Google Groups "opencog" group.
            To unsubscribe from this group and stop receiving emails
            from it, send an email to [email protected].
            To post to this group, send email to [email protected].
            Visit this group at https://groups.google.com/group/opencog.
            To view this discussion on the web visit
            
https://groups.google.com/d/msgid/opencog/18e0a808-96d2-4740-8213-c115a8a7255a%40googlegroups.com
            
<https://groups.google.com/d/msgid/opencog/18e0a808-96d2-4740-8213-c115a8a7255a%40googlegroups.com?utm_medium=email&utm_source=footer>.
            For more options, visit https://groups.google.com/d/optout.

-- You received this message because you are subscribed to the Google
    Groups "opencog" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to [email protected]
    <mailto:[email protected]>.
    To post to this group, send email to [email protected]
    <mailto:[email protected]>.
    Visit this group at https://groups.google.com/group/opencog.
    To view this discussion on the web visit
    
https://groups.google.com/d/msgid/opencog/6862df1e-8b77-4563-a0e5-6601fb505206%40googlegroups.com
    
<https://groups.google.com/d/msgid/opencog/6862df1e-8b77-4563-a0e5-6601fb505206%40googlegroups.com?utm_medium=email&utm_source=footer>.
    For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "opencog" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>. To post to this group, send email to [email protected] <mailto:[email protected]>.
Visit this group at https://groups.google.com/group/opencog.
To view this discussion on the web visit https://groups.google.com/d/msgid/opencog/CADbdzdz3a-N2TtV5iRvZPdh-_gNkGQQE19KAh5YJVSMpVPN%3DJA%40mail.gmail.com <https://groups.google.com/d/msgid/opencog/CADbdzdz3a-N2TtV5iRvZPdh-_gNkGQQE19KAh5YJVSMpVPN%3DJA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups 
"opencog" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/opencog.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/opencog/6c88b141-3deb-b937-174f-23319806e835%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to