Actions

Copy link

Testing #894

closed

Generate release candidates builds: Harkonnen

Added by Hammel over 3 years ago. Updated about 2 years ago.

Status:

Closed

Priority:

Immediate

Assignee:

Hammel

Category:

09 - Testing

Target version:

2.0 - Harkonnen

Start date:

14 Apr 2022

Due date:

% Done:

100%

Estimated time:

Severity:

02 - High

Description

By the time I get to this issue then all coding should be done for the Harkonnen release.
That means I need to do a full build of the dev platform and all system packages.
A full build will be done twice.

Locally, using cached downloads
On colo server without using cached downloads, to verify a clean build.

Once the builds are completed, then the System Integration Testing (RM #893) will be run.
This issue won't be closed until RM #893 is completed - they will be closed together.

Version Bump¶

All repos need a version bump before final builds. This requires updating Metabuild's repolist.txt with new app repos. Check all the pkglist.* files for repos that need to be included in repolist.txt.

After version bumps the following libraries need to have their archives updated for PiBox dev platform builds.

libpibox
pibox-network-config

Build Matrix¶

Versioned means the repos have had their version number bumped to 2.0.

Build	RPi 1	RPi 2	RPi 3	Zero (3)	Zero W	Linux Host	Versioned
Build	Hardware						Versioned
Dev Platform	x	x	x	x	x		x
Media System		x	x				x
Media Player	x	x	x				x
Kiosk	x	x	x	x	x		x
Auto Kiosk		x	x	x	x		x
PiStore		x	x				x
PiSentry		x	x				x
Desktop (VideoLib)						x	x

Related issues

Actions

Copy link

Updated by Hammel over 3 years ago

Severity changed from 03 - Medium to 02 - High

Actions

Copy link

Updated by Hammel over 3 years ago

Description updated (diff)

Actions

Copy link

Updated by Hammel over 3 years ago

Description updated (diff)

Actions

Copy link

Updated by Hammel almost 3 years ago

Errors on version bump

ironman+www

./build.sh: line 278: ironman+www: command not found
./build.sh: line 162: cd: /home/mjhammel/src/ximba/metabuild/src/../bld/xeoncfg: No such file or directory
Cloning into '/home/mjhammel/src/ximba/metabuild/src/../bld/xeoncfg'...
X11 forwarding request failed on channel 0
remote: Enumerating objects: 60, done.
remote: Counting objects: 100% (60/60), done.
remote: Compressing objects: 100% (32/32), done.
remote: Total 60 (delta 20), reused 57 (delta 19), pack-reused 0
Receiving objects: 100% (60/60), 11.21 KiB | 11.21 MiB/s, done.
Resolving deltas: 100% (20/20), done.
fatal: not a git repository (or any parent up to mount point /home/mjhammel/src)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: not a git repository (or any parent up to mount point /home/mjhammel/src)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

pitemplate

error: pathspec 'version.txt' did not match any file(s) known to git
X11 forwarding request failed on channel 0
Everything up-to-date

Actions

Copy link

Updated by Hammel almost 3 years ago

Description updated (diff)

Actions

Copy link

Updated by Hammel almost 3 years ago

% Done changed from 0 to 20

Both versionRepos() and tagRepos() in build.sh needed to be updated to handle func+proj entries in the repolist.txt file. Both are tested locally and seem to work correctly for all repolist.txt entries. versionRepos() was used to actually update ironman+www.

pitemplate is not structured correctly and really doesn't need versioning. So it's been commented out in repolist.txt.

Actions

Copy link

Updated by Hammel almost 3 years ago

Description updated (diff)

After version bump of all repos, dev platform builds (rpi/rpi2) on both servers (local/colo) have been updated.

Rebuilding all system packages on both servers.

Actions

Copy link

Updated by Hammel almost 3 years ago

Description updated (diff)

Actions

Copy link

Updated by Hammel almost 3 years ago

Description updated (diff)

Actions

Copy link

#10

Updated by Hammel almost 3 years ago

Status changed from New to In Progress

Actions

Copy link

#11

Updated by Hammel almost 3 years ago

% Done changed from 20 to 70

Builds for all systems completed on both local and colo servers.

Now testing will be done. See RM #893.

Actions

Copy link

#12

Updated by Hammel almost 3 years ago

Found two bugs in packaging while preparing for testing.

Both rpi1 and rpi2 builds are missing firmware directory after make pkg is run.
The rpi1 build is missing its opkg directory after make pkg is run.

The first one is weird, but might be a networking problem in docker:

$ make HW=rpi rpifw-pkg
###  2022-09-19 10:51:30 PM Firmware source is cached - pulling latest 
fatal: unable to connect to github.com:
github.com[0: 140.82.114.4]: errno=Connection timed out

make: *** [configs/rpifirmware.mk:7: .rpifw-get] Error 1

Turns out this is because GitHub (where the RPi firmware is stored) doesn't do git:// anymore, but the configs/rpifirware-git.cfg was using it. Switching the archive to https as such

git remote set-url origin https://github.com/raspberrypi/firmware.git

and then changing the .cfg to use https seems to fix the problem. However, the .mk should still die if the git commands fail. They didn't which is why I didn't catch this failure. I should note that the builds both local and on the colo hit this problem opaquely.

Actions

Copy link

#13

Updated by Hammel almost 3 years ago

Second problem is not clear, but I think it was an artifact of the way I did the full build on the local machine. If I remove the .xcc-opkg and .xcc-opkg-pkg stamp files and then run