Docker usage issue with version 3.2.1.post46+g8f69adc about agvis HOT 6 CLOSED

I tested ./go.sh build and ./go.sh dev2 on the develop branch and it works on Linux. Can you tell me the branch you are using and can you send me the go.sh file that caused the issue?

from agvis.

Nevermind, I see the issue. I accidentally added a '!' at the end of the line that failed. That is not valid syntax and it is weird that the script would even compile on my end. The issue should be fixed on develop.

from agvis.

I was using Mac OS.

BTW, in the excerpted preamble message, there is a line says, "Python 3.11.6 on Darwin, 10/20/2023 03:16:01 PM". Three most common options are Windows, Linux, and Darwin, where Darwin is the core UNIX OS of Mac OS.

I tested ./go.sh build and ./go.sh dev2 on the develop branch and it works on Linux. Can you tell me the branch you are using and can you send me the go.sh file that caused the issue?

from agvis.

Is it possible to include the Docker part check as part of GitHub flow?

In the AGVis unit test part, we can focus on the Python module functionality, whereas Docker is hard to be included here. Therefore, GitHub flow can be a good choice as the Docker functionality test.

from agvis.

By GitHub flow do you mean creating a separate branch specifically for Docker testing?

I might be able to include the ./go.sh commands as a part of the agvis test command, but I have not looked into this yet.

from agvis.

By GitHub flow do you mean creating a separate branch specifically for Docker testing?

I might be able to include the ./go.sh commands as a part of the agvis test command, but I have not looked into this yet.

GitHub flow means, we can pre-define some jobs in the AGVis repository. Then, GitHub will create some check on PR, where we can include some complex testing actions. Such as building documentation on ReadTheDocs, running built-in AGVis tests.

Not sure which one is more easier, we can discuss on next Monday's monthly meeting if you can attend it.

from agvis.