checkImageVersionFrom (Replacement/generated/64/vm/src/gcc3x-cointerp.c:62402):Invalid image format: detected version 6521, expected version 68021

[vonbecmann]

the
http://files.pharo.org/get-files/90/pharo-vm-Linux-x86_64-stable.zip
vm cannot open the image
http://files.pharo.org/get-files/90/pharoImage-x86.zip

see
https://github.com/vonbecmann/linked-list/runs/7512038823?check_suite_focus=true#step:4:37

[vonbecmann]

im trying to test the project in this Pharo32-9.0 environment, but it doesn't open the image with that vm.

[fniephaus]

It looks like you're trying to open a 32-bit image on a VM for 64-bit images. Does that even work?

[vonbecmann]

does this framework choose the image and vm? im just adding Pharo32-9.0 to the config file.

[fniephaus]

Yes, it does. Maybe the Pharo zeroconf configuration is broken. @estebanlm?

[vonbecmann]

that vm is not the adequate for that image. i'll ask the pharo development team for a suitable vm.

[fniephaus]

Ok, good. If you found out what's wrong, please feel free to update the VM map:

smalltalkCI/pharo/run.sh

Lines 137 to 208 in b35b5c5

	pharo::get_vm_url() {
	local smalltalk_name=$1
	case "${smalltalk_name}" in
	# NOTE: vmLatestXX should be updated every time new Pharo is released
	"Pharo64-alpha")
	echo "get.pharo.org/64/vmLatest110"
	;;
	"Pharo64-stable")
	echo "get.pharo.org/64/vm100"
	;;
	"Pharo64-11")
	echo "get.pharo.org/64/vm110"
	;;
	"Pharo64-10"|"Moose64-10"|"Moose64-trunk")
	echo "get.pharo.org/64/vm100"
	;;
	"Pharo64-9.0"|"Moose64-9.0")
	echo "get.pharo.org/vm90"
	;;
	"Pharo64-8.0"|"Moose64-8.0")
	echo "get.pharo.org/64/vm80"
	;;
	"Pharo64-7.0"|"Moose64-7.0")
	echo "get.pharo.org/64/vm70"
	;;
	"Pharo64-6.1")
	echo "get.pharo.org/64/vm61"
	;;
	"Pharo64-6.0")
	echo "get.pharo.org/64/vm60"
	;;
	"Pharo32-alpha"|"Pharo-alpha")
	echo "get.pharo.org/vmLatest110"
	;;
	"Pharo-stable"|"Pharo32-stable")
	echo "get.pharo.org/vm100"
	;;
	"Pharo32-11")
	echo "get.pharo.org/vm110"
	;;
	"Pharo32-10")
	echo "get.pharo.org/vm100"
	;;
	"Pharo32-9.0")
	echo "get.pharo.org/vm90"
	;;
	"Pharo32-8.0"|"Moose32-8.0"|"Moose32-trunk")
	echo "get.pharo.org/vm80"
	;;
	"Pharo32-7.0"|"Pharo-7.0"|"Moose32-7.0"|"Moose-7.0")
	echo "get.pharo.org/vm70"
	;;
	"Pharo32-6.1"|"Moose32-6.1"|"Pharo-6.1"|"Moose-6.1")
	echo "get.pharo.org/vm61"
	;;
	"Pharo32-6.0"|"Pharo-6.0")
	echo "get.pharo.org/vm60"
	;;
	"Pharo32-5.0"|"Moose32-6.0"|"Pharo-5.0"|"Moose-6.0")
	echo "get.pharo.org/vm50"
	;;
	"Pharo32-4.0"|"Pharo-4.0")
	echo "get.pharo.org/vm40"
	;;
	"Pharo32-3.0"|"Pharo-3.0")
	echo "get.pharo.org/vm30"
	;;
	*)
	print_error_and_exit "Unsupported Pharo version '${smalltalk_name}'."
	;;
	esac

[estebanlm]

no, that's not an error.
You are downloading a 32bit image but the infrastructure where you run the test is 64bit, hence, zeroconf downloads the appropriate VM for that architecture automatically... and your 32bit image wont work.

[fniephaus]

Mh, so how do we force download a 32-bit VM on a 64-bit GitHub action runner? We do install 32-bit dependencies on those machines.

[estebanlm]

we are not interested on support such a feature (which is really hard to maintain). instead, I would require a 32bit machine to test 32bit images.

…

On Aug 16 2022, at 9:36 am, Fabio Niephaus ***@***.***> wrote: Mh, so how do we force download a 32-bit VM on a 64-bit GitHub action runner? We do install 32-bit dependencies on those machines. — Reply to this email directly, view it on GitHub (#563 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AAD5MXSN4IYDD7SVY6ACADDVZNAJPANCNFSM56S5OTIA). You are receiving this because you were mentioned.

[fniephaus]

Ok, well that means that you cannot test Pharo32 anymore on any popular CI provider (I'm not aware of any provider supporting 32-bit machines) unless you provide your own 32-bit machine.

[estebanlm]

well, there is a reason why nobody provides 32bit machines anymore and is that nobody uses 32bit machines anymore. to be honest, we are still producing 32bit images more thinking on arm architectures, some of them still live in 32bit, than on x86 architectures, yet there is a 32bit intel VM, you can force the download and prepare the dependencies... but zeroconf is not prepared anymore to do that... anyway, I will let @tesonep to answer completely as the detail escapes me.

…

On Aug 16 2022, at 10:05 am, Fabio Niephaus ***@***.***> wrote: Ok, well that means that you cannot test Pharo32 anymore on any popular CI provider (I'm not aware of any provider supporting 32-bit machines) unless you provide your own 32-bit machine. — Reply to this email directly, view it on GitHub (#563 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AAD5MXVPVRUJ3NHE5WMDRITVZNDURANCNFSM56S5OTIA). You are receiving this because you were mentioned.

[vonbecmann]

in my opinion, just remove that environment as an option.