https://issues.dlang.org/show_bug.cgi?id=21053

Walter Bright <bugzilla@digitalmars.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |TestSuite

--

https://issues.dlang.org/show_bug.cgi?id=21053

Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dlang-bugzilla@thecybershad
                   |                            |ow.net

--- Comment #1 from Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> ---
dmd/test/Makefile contains:

# Build d_do_test here to run it's unittests
# TODO: Migrate this to run.d
$(RUNNER): run.d $(RESULTS_DIR)/d_do_test$(EXE)
        $(RUN_HOST_DMD) $(MODEL_FLAG) $(PIC_FLAG) -g -od$(RESULTS_DIR)
-of$(RUNNER) -i -release $<


So, it looks like this is already the case?

--

https://issues.dlang.org/show_bug.cgi?id=21053

moonlightsentinel@disroot.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |moonlightsentinel@disroot.o
                   |                            |rg

--- Comment #2 from moonlightsentinel@disroot.org ---
Partially, it's done for all CI which have an appropriatly recent host compiler, otherwise it falls back to the generated dmd. This affects a few CI machines which will update to an appropriate compiler eventually once we raise the minimally required bootstrap version.

--

https://issues.dlang.org/show_bug.cgi?id=21053

--- Comment #3 from moonlightsentinel@disroot.org ---
*** Issue 21126 has been marked as a duplicate of this issue. ***

--

https://issues.dlang.org/show_bug.cgi?id=21053

--- Comment #4 from Walter Bright <bugzilla@digitalmars.com> ---
(In reply to moonlightsentinel from comment #2)
> Partially, it's done for all CI which have an appropriatly recent host compiler, otherwise it falls back to the generated dmd. This affects a few CI machines which will update to an appropriate compiler eventually once we raise the minimally required bootstrap version.

Why can't simply the previous release be used?

After all, recent experience shows that using the compiler under test makes for a very time consuming and miserable debugging experience, since run.d manages to use all of Phobos and every feature in D :-/

I.e. it requires everything, Phobos and all, to be working before it can run a single test.

Either that, or simply supply a pre-built known-working executable to be used to drive the tests.

--

https://issues.dlang.org/show_bug.cgi?id=21053

Dlang Bot <dlang-bot@dlang.rocks> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |pull

--- Comment #5 from Dlang Bot <dlang-bot@dlang.rocks> ---
@wilzbach updated dlang/dmd pull request #11519 "Make -lowmem optional and prefer building d_do_test with the host compiler" fixing this issue:

- Fix Issue 21053 - Make -lowmem optional and prefer building d_do_test with the host compiler

https://github.com/dlang/dmd/pull/11519

--

https://issues.dlang.org/show_bug.cgi?id=21053

--- Comment #6 from moonlightsentinel@disroot.org ---
(In reply to Walter Bright from comment #4)
> Why can't simply the previous release be used?

Because one would need to install it on the auto-tester machines to which only one person (Brad?) has access AFAICT. Otherwise we would have to download a release which could fail spuriosly as well.

> since run.d manages to use all of Phobos and every feature in D :-/


That statement is just blatantly wrong.

--

https://issues.dlang.org/show_bug.cgi?id=21053

--- Comment #7 from Walter Bright <bugzilla@digitalmars.com> ---
(In reply to moonlightsentinel from comment #6)
> That statement is just blatantly wrong.

The list of its imports, and the imports of those imports, doesn't leave out much. It would be nigh impossible to attempt to run that as the first program when porting to a new architecture.

> Because one would need to install it on the auto-tester machines to which only one person (Brad?) has access AFAICT. Otherwise we would have to download a release which could fail spuriosly as well.

I suggest using whatever bootstrap compiler is installed on it. There's no particular reason it should require the latest features and phobos. If the same compiler is used to build it, it shouldn't suddenly stop working.

--

https://issues.dlang.org/show_bug.cgi?id=21053

Dlang Bot <dlang-bot@dlang.rocks> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Dlang Bot <dlang-bot@dlang.rocks> ---
dlang/dmd pull request #11519 "Make -lowmem optional and prefer building d_do_test with the host compiler" was merged into master:

- 04927dc32b9007ef75042b446ce444d62f189646 by Sebastian Wilzbach:
  Fix Issue 21053 - Make -lowmem optional and prefer building d_do_test with
the host compiler

https://github.com/dlang/dmd/pull/11519

--