A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/agda/agda/issues/6933 below:

size-solver-test rebuilds Agda · Issue #6933 · agda/agda · GitHub

See e.g. this CI run: https://github.com/agda/agda/actions/runs/6577500740/job/17869278492

  1. 15m 40s Build Agda
  2. 13m 46s Run tests for the size solver

Compare this with pre #6863 run https://github.com/agda/agda/actions/runs/6510947029/job/17685706260

  1. 14m 10s
  2. 26s

Post #6863 run https://github.com/agda/agda/actions/runs/6534521998/job/17741904793

  1. 13m 31s
  2. 11m 51s

So this is likely a regression introduced by

This PR changed the default flags for building Agda (adding -f debug to preserve debug printing facility) which have not been likewise changed in

install-bin : ifdef HAS_STACK $(STACK) build size-solver $(STACK_INSTALL_OPTS) mkdir -p dist/build/size-solver cp $(shell $(STACK) path --local-install-root)/bin/size-solver dist/build/size-solver/size-solver else $(CABAL) $(CABAL_INSTALL_CMD) $(CABAL_INSTALL_OPTS) endif

ATTN:

@AndrasKovacs

The question is whether we need the size-solver-test at all in CI.
In #6932 I added commit be28b6e to switch it off (hot fix to recover CI times).

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4