Asof Feb 21st, when CodeQL-Build (c++) executes unit tests it gets stuck. But on Feb 2 the same code passes all of thus unit tests

[SwuduSusuwu]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

Schedule & Cron Jobs

Discussion Details

https://github.com/copilot/share/801f018e-40e0-8822-9152-e04800a36057 includes all of the specifics to reproduce this.


On Feb 2, those GitHub workflows just executed for 6 minutes (then showed this source code passes all unit tests). Was concerned that (on GitHub) such smple unit tests took 6 whole minutes (on an old Core 2 Duo laptop with Ubuntu those tests just 2 minutes to pass, on a smartphone those tests also took 2 minutes to pass (but with TensorFlow tests skipped on the smartphone)).
After GitHub's last "update", those same GitHub workflows execute 6 hours on this source code (then are cancelled), although the source code is as on Feb 2 How to go back to old GitHub Actions versions?

[SwuduSusuwu]

https://github.com/copilot/share/801f018e-40e0-8822-9152-e04800a36057 suggests that the solution is just to disable the next unit test, then disable the next unit test, then disable the next unit test (all of which used to pass for this source code), but no matter how many unit tests are disabled, the GitHub's CodeQL workflow still gets stuck/cancelled. until all unit tests are disabled:

• SwuduSusuwu/SusuLib@2a9376a reverted, since classWebBrowseTests() passes.
• SwuduSusuwu/SusuLib@01bb18b
• SwuduSusuwu/SusuLib@d2e782f
• SwuduSusuwu/SusuLib@a73bc4c reverted, replaced with SwuduSusuwu/SusuLib@cccfc16 (which just disables the XHTML parser component of the unit test).

---

Wish to know what (except disable tests which used to pass) to do (how to troubleshoot this).

[SwuduSusuwu]

Most GitHub "updates" are regressions (one of the recent GitHub Actions "updates" prevents Codacy scanner use (can not execute no matter how many suggested solutions are followed)) so switched to CodeQL, which now also can not execute simple unit tests.

Is GitHub "sick" now? Should switch from git to Bazaar? Or from GitHub to some other git distributed host?

[SwuduSusuwu]

Steps to reproduce successful unit tests (all passes) for Ubuntu (or for smartphones):

git clone https://github.com/SwuduSusuwu/SusuLib.git
cd SusuLib
git switch preview
./build.sh

, for Windows: replace ./build.sh with ./build --mingw.

[SwuduSusuwu]

Haiku suggests that one possible reason those unit tests all of a sudden got stuck is: GitHub Action's Docker image changes

[SwuduSusuwu]

From the discussion with Haiku:

https://github.com/SwuduSusuwu/SusuLib/actions/runs/21374657409/job/61527745576 shows that SwuduSusuwu/SusuLib@eb604c0 passes all unit tests.

GitHub's /compare/ tool shows that this source code (which has CodeQL-Build (c++)'s Autobuild (which, through ./build.sh, includes unit tests) stuck) has no changes since when those unit tests passed.