Skip to content

CI: Use the test scripts from Dosemu - #130

Merged
stsp merged 2 commits into
dosemu2:masterfrom
andrewbird:ci-102
Sep 17, 2026
Merged

stsp merged 2 commits into
dosemu2:masterfrom
andrewbird:ci-102

Conversation

@andrewbird

@andrewbird andrewbird commented Sep 9, 2026

Copy link
Copy Markdown
Member

1/ Test comcom32/64 using the suite from dosemu2
2/ Split the publishing build into a separate step from test.

@andrewbird
andrewbird marked this pull request as ready for review September 11, 2026 17:35
@andrewbird

Copy link
Copy Markdown
Member Author

This is okay to review now, please.

Comment thread ci_test.sh
@andrewbird
andrewbird force-pushed the ci-102 branch 8 times, most recently from d21b8a4 to 1c7c5e1 Compare September 15, 2026 10:21
@andrewbird

Copy link
Copy Markdown
Member Author

Should be better now.

Comment thread ci_build_deploy.sh Outdated

set -e

sudo apt install -f -y dj32-dev

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You have that in test_prereq, no?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do, but somehow it's gone by the time I need it for the deployment build, I couldn't figure out why. See https://github.com/dosemu2/comcom64/actions/runs/34953272048/job/104329103722#step:11:66

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are many things that are
going wrongly:

dj32-dev is already the newest version (0.5-0~202608232226+202608240133~ubuntu22.04.1).
dj32-dev set to manually installed.
comcom32 is already the newest version (0.5-1).
comcom64 is already the newest version (0.5-1).

So it didn't even install the just-built comcoms,
taking the ones from PPA I suppose. And dj32-dev
was already installed.

Then you have this:

The following packages will be REMOVED:
  comcom64-build-deps dj32-dev gcc-11-i686-linux-gnu gcc-i686-linux-gnu

Its strange that it removes whatever was
manually installed, but you need to figure
out why you have so many "already the newest
version" messages, that indicate a flaws.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it didn't even install the just-built comcoms,
taking the ones from PPA I suppose.

Well that's no good. Earlier I had used 'dch' to update the changelog as I'd noticed that when using the packaged binaries for deployment, the timestamps were old. I removed that when going back to the static build process. The thing is I have dosemu PPA added so that I can get dosemu and fdpp, and of course comcom can be found from there if the just built package is deemed older.

I'll have another try.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems that gcc-multilib (just copy pasted from dosemu test prerequisites, but not actually used here) conflicts with comcom64-build-deps dj32-dev gcc-13-i686-linux-gnu gcc-i686-linux-gnu causing removal (even without -f / or -y flags to apt install).

Anyway I can remove that gcc-multilib package install (it's only used for process tests I think).

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

have to go out now, back later.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I am starting to recall that
gcc-multilib conflicts (and removes)
all i386 cross-compilers, and thus
dj32-dev.
We need to eliminate gcc-multilib
from everywhere, including dosemu2
itself! Can you give that a try?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems better now as Comcom tests don't need multilib. On Dosemu multilib is only needed for one fpu test to produce the reference file. We could add that to git, but we'd probably need to compress it first as it's 57 MiB.

@andrewbird
andrewbird force-pushed the ci-102 branch 5 times, most recently from 842ffc0 to 184c4c2 Compare September 16, 2026 17:17
Test comcom32/64 using the suite from dosemu2
The build of comcom32/64 for the pages doesn't belong in the
ci_test.sh script, so move it to a separate script.
@stsp
stsp merged commit f639578 into dosemu2:master Sep 17, 2026
1 check passed
@stsp

stsp commented Sep 17, 2026

Copy link
Copy Markdown
Member

Thanks!

@stsp

stsp commented Sep 17, 2026

Copy link
Copy Markdown
Member

@andrewbird

Copy link
Copy Markdown
Member Author

Okay, I understand what it is, will work on a fix.

@andrewbird
andrewbird deleted the ci-102 branch September 17, 2026 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants