Create Github action to Test Browser Build

[tmbrbr]

We had a Github action to build the full browser a while ago, but it was fairly flakey due to memory limitations.

Trying again to see if there is more stability now.

One advantage now is that there are also windows and mac runners, which could eventually lead to automated builds for those targets.

Note: this needs to be tested as an open pull request, as I think the SAP action runners have slightly different configurations compared to my personal account.

Successful build targets so far:

• Ubuntu
• Windows
• MacOS 14 (M1 silicon)
• MacOS 13 (Intel Silicon)

[tmbrbr]

Current iteration passes the build step, but packaging fails with:

System.IO.IOException: No space left on device

[tmbrbr]

Some disk usage statistics, before build (ie after the checkout):

Filesystem      Size  Used Avail Use% Mounted on
/dev/root        73G   56G   17G  77% /
tmpfs           7.9G  172K  7.9G   1% /dev/shm
tmpfs           3.2G  1.1M  3.2G   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sdb15      105M  6.1M   99M   6% /boot/efi
/dev/sda1        74G  4.1G   66G   6% /mnt
tmpfs           1.6G   12K  1.6G   1% /run/user/1001

[tmbrbr]

Mozilla states around 30Gb is required for a build: https://firefox-source-docs.mozilla.org/setup/linux_build.html.

[tmbrbr]

The default GitHub runners have a lot of stuff installed to be able to build just about everything (Docker images, Android SDKs, Node.js, Java, ...).

See for example this ticket: actions/runner-images#10386

There are Actions plugins available to free up space: https://github.com/marketplace/actions/free-disk-space-ubuntu

[tmbrbr]

All checks have passed! 🎉

[tmbrbr]

At the moment there is an issue that bash cannot find /tmp. After some research it seems it is related to the fact that the bash shell shipping with MSYS does not respect the TEMP/TMP environment variables:

msys2/MSYS2-packages#334
https://sourceforge.net/p/msys2/mailman/message/34925671/

[tmbrbr]

The underlying problem is that extracting mozilla build tools via 7z does not contain all the directories needed by the installer (including tmp).

[tmbrbr]

Now the build is starting but we are into the actual build errors! The good news is that it looks like a windows build is in principle possible via github actions! 🎉

The error message is:

 8:16.29 error[E0282]: type annotations needed for `Box<_>`
 8:16.29   --> D:\a\project-foxhound\project-foxhound\third_party\rust\time\src\format_description\parse\mod.rs:83:9
 8:16.29    |
 8:16.29 83 |     let items = format_items
 8:16.29    |         ^^^^^
 8:16.29 ...
 8:16.29 86 |     Ok(items.into())
 8:16.29    |              ---- type must be known at this point
 8:16.29    |
 8:16.29    = note: this is an inference error on crate `time` caused by an API change in Rust 1.80.0; update `time` to version `>=0.3.35` by calling `cargo update`
 8:17.37 For more information about this error, try `rustc --explain E0282`.

The bootstrap installs Rust 1.84 by default, according to https://firefox-source-docs.mozilla.org/writing-rust-code/update-policy.html we need Rust 1.77.2.

We need to do something similar to the build script: https://github.com/sap/project-foxhound/blob/main/build.sh#L146

[tmbrbr]

All checks have passed!! 🎉

[tmbrbr]

I am impressed with how stable the GitHub runner builds are by now. I remember a few years ago we kept running into memory problems and the jobs kept getting killed!

[leeN]

LGTM

[leeN]

LGTM