tools/run_all_tests_from_cron:
10.04 is now the release branch.
tools/test_mercury:
Prepare for building the 10.04 branch.
Delete stuff related to the 0.13 branch.
tools/run_all_tests_from_cron:
tools/test_mercury:
Add the necessary entries for goliath and bob.
Update the beta FTP directory - it's now hosted on uranus
not earth.
Delete stuff related to earth and aral, which are no longer
in use.
Delete stuff related to uranus, it shouldn't be doing
Mercury builds.
Estimated hours taken: 0.2
Branches: main
Re-arrange some of the nightly tests, mainly in order to reduce the load
on swordfish.
tools/test_mercury:
Remove stuff related to uranus - this machine will not be
used for general testing of Mercury.
Remove stuff related to ceres since it is now dead.
Remove the G12_ROTD_HOST stuff - we never really used it.
Dial down the optimization level used on swordfish since with
the current load the regression tests are taking longer than
24 hours.
Remove stuff related to mundroo.
Install .trseg grades on swordfish in place of .tr grades.
tools/run_all_tests_from_cron:
s/pluto/goofy/
Estimated hours taken: 1
Branches: main
Change some of our test infrastructure to avoid using /home/mercury where possible.
This will mean that test runs can complete, even in situations where /home/mercury
becomes inacessible.
tools/test_mercury:
Avoid (un)tagging the repository after each test run.
(If anyone wants to checkout the specific version used in a test run they
can do so using the start time which is recorded at the beginning of the log.)
This will prevent the situation that sometimes occurs now where mulitple machines
tie up the repository because they are all trying to simultaenously (un)tag
it.
tools/run_all_tests_from_cron:
Write the of logs of the nightly tests to a local filesystem rather
than to /home/mercury. (We will set up symbolic links from /home/mercury
to point to these logs.)
Estimated hours taken: 4
Branches: main
Modify nightly test scripts to allow testing with `mmc --make' and testing of
the erlang grade.
tools/run_all_tests_from_cron:
Accept a fourth command line argument to enable testing
with mmc --make (which should be `--use-mmc-make' in that case).
Pass this to test_mercury.
tools/test_mercury:
Accept the additional --use-mmc-make option. Pass that to all
calls of mmake and bootcheck.
Make ceres install and test the erlang grade if called with
--use-mmc-make.
Estimated hours taken: 0
Branches: main
tools/run_all_tests_from_cron:
Don't test the release branch for now; if it becomes
necessary to release 0.13.2 we can start testing it
again.
Estimated hours taken: 0
Branches: main
tools/test_mercury:
Set up for building the next g12 Mercury relase.
tools/run_all_tests_from_cron:
Test the release branch on earth and ceres.
Estimated hours taken: 0.1
Branches: main
tools/run_all_tests_from_cron:
Begin building 0.13-betas on jupiter. (I'll sort the other machines out later
this week.)
Estimated hours taken: 0.5
Branches: main
tools/run_all_tests_from_cron:
Fix a typo: s/juptier/jupiter/
tools/test_mercury:
Setup nightly tests on five of the six machines we have
borrowed for summer (leopard is being used for benchmarking).
Remove stuff related to ender, roy and hg and these hosts
are now retired.
Estimated hours taken: 0
Branches: main
tools/run_all_tests_from_cron:
Send the results of the nightly builds to me rather
than Zoltan while he is away.
Estimated hours taken: 0
Branches: main
tools/run_all_tests_from_cron:
Build 0.12.1-beta on jupiter.
Balance the testing schedule so that about half the machines are
building the release branch on alternate nights.
Estimated hours taken: 0.1
Branches: main
tools/run_all_tests_from_cron:
Setup for weekly tests on mundula.
Delete stuff related to saskervoy (one of the machines we borrowed
last summer).
Test the release branch on swordfish.
Estimated hours taken: 1
Branches: main
tools/run_all_tests_from_cron:
tools/test_mercury:
Add /usr/bin to the PATH so that basic commands like cp can be run.
ulimit doesn't seem to work properly on cygwin, so disable it for
uranus.
Enable nightly builds on uranus.
Estimated hours taken: 1
Branches: main and 0.12
Remove the architecture string from the installed directory structure
and put the executables in $PREFIX/bin, instead of
$PREFIX/lib/mercury/bin/$FULLARCH.
The reason for this change is to reduce the need for unix shell scripts in
the top-level bin directory that call the actual programs in the
lib/mercury/bin/FULLARCH directory. The unix scripts can't be run on Windows
without a unix emulation environment like Cygwin.
Because the executables are now in the top-level bin directory, we cannot
install multiple architectures under the same directory structure. However
this is not a real loss, since the binaries for different architectures can
just be installed to different locations, as we currently do anyway on
mundula.cs.mu.oz.au.
The plan is to rename mercury_compile to mmc and do away with the mmc unix
script. This will allow mmc to be run on Windows without Cygwin or MSYS.
This proposal replaces a previous proposal to implement a C version of the
mmc script. That solution turned out to be quite complicated and
unreliable.
This diff will also mean mdice, mslice and mtc_union will be in the same
directory as mmc, so will be in the PATH as long as mmc is in the PATH.
configure.in:
bindist/Mmakefile:
bindist/bindist.Makefile.in:
compiler/compile_target_code.m:
compiler/handle_options.m:
compiler/make.program_target.m:
debian/rules:
library/Mmakefile:
scripts/Mmake.vars.in:
scripts/mdprof.in:
scripts/mercury.bat.in:
scripts/mgnuc.in:
scripts/ml.in:
scripts/mmc.in:
scripts/mprof.in:
tools/run_all_tests_from_cron:
tools/test_mercury:
Remove FULLARCH from the installed directory structure.
Install executables to the top-level bin directory.
Estimated hours taken: 0.1
Branches: main
tools/run_all_tests_from_cron:
Don't build the release branch on swordfish.
Delete entries related to almery and ascolais,
we no longer have these machines.
Estimated hours taken: 0.1
Branches: main, release
Setup to test the release branch on linux/x86.
aral/jupiter - main branch only
earth/saskervoy/ceres - release on odd numbered days
almery/ascolais/swordfish - release on even numbered days
hg/ender - main branch (if anything)
tools/run_all_tests_from_cron:
Start testing the release branch.
Estimated hours taken: 0.1
Branches: main, release
tools/run_all_tests_from_cron:
Update this script in preparation for the 0.12 release.
Delete references to hosts that no longer exist.
Estimated hours taken: 1
Branches: main
tools/run_all_tests_from_cron:
Fix a bug where the tests on taifun were all being run on
the main branch, rather than (as the documentation here suggested)
testing the release branch once a week.
The problem was that this script was only running the release
branch when day = 6 (Saturday), but the tests on taifun
were only being run on Sun, Wed, and Fri, not Sat.
I changed the script to test for day = 6 or day = 0.
Estimated hours taken: 0.25
Branches: main
tools/run_all_tests_from_cron:
- Test both the 0.11 branch and the main branch,
rather than concentrating on the 0.11 branch.
Estimated hours taken: 0.25
Branches: main
tools/run_all_tests_from_cron:
A temporary change, for while we're preparing for the new release:
run most of the tests on the release branch rather than the main
branch.
Estimated hours taken: 0.25
Branches: main
Some more changes to make it easier to run our nightly tests on new hosts.
tools/run_all_tests_from_cron:
Create the necessary directories automatically if they don't exist
already.
Ensure that we use the version of config.guess from the Mercury CVS
repository, rather than assuming it will be in the PATH.
Estimated hours taken: 2
Branches: main
tools/run_all_tests_from_cron:
tools/test_mercury:
Some changes to make the tests work on machines that are not part
of the Mercury network (i.e. that don't NFS-mount /home/mercury):
- Use $HOME/public rather than /home/mercury/public if the latter
doesn't exist.
- Don't make files group-writable unless /home/mercury/public
exists.
- Remove some obsolete directories (gcc-2.7.2, egcs, nu-prolog,
sicstus3) from the PATH.
- Simplify the logic for which bootstrap compiler to use.
- Avoid hard-coding the list of hosts and their architectures,
grades, etc.
Mmakefile:
Add `echo_libgrades' target, for use by tools/test_mercury.
Estimated hours taken: 1
Branches: main
Various minor fixes to the nightly tests.
tools/run_all_tests_from_cron:
- Test on mundroo.
- Fix a bug where it was not preserving the old `.test_errs' files.
- Fix a bug where there was a syntax error in a call to grep,
which lead to incorrect output in the cron email.
- Fix a bug where it was listing the wrong copy of `mercury_compile'
in the cron email.
tools/test_mercury:
- Test lcc on mars.
- Use GCC 3.2 rather than 3.0 for the native code back-end.
Estimated hours taken: 30
Branches: main
Improve the test framework to make it easier to find out which tests
failed and to reduce disk usage (important in debug grades).
Allow the tests to be run with `mmc --make' (still some failures).
Allow the user to run only the failing tests from a previous
run by using `mmake ERROR_FILE=runtests.errs', where runtests.errs
is the log file from the previous run.
tests/Mmake.common:
tests/*/Mmakefile:
Move common code (such as the code to deal with subdirectories)
to Mmake.common.
Run the tests using `mmake runtests' rather than using slightly
different runtests scripts in each directory.
Add to the output from `mmake runtests' to make it easier to
identify which tests failed in which grades.
Move per-module options into Mercury.options files so they
can be read by `mmc --make'.
Remove the last of the NU-Prolog support.
Consistently use the main module name when listing tests.
Some directories (e.g. invalid) were using the source file
name.
tests/process_log.awk:
Collect the parts of the output relating to failing tests.
tests/generate_exp:
tests/handle_options:
tests/subdir_runtests:
tests/startup:
tests/shutdown:
tests/*/runtests:
tests/recompilation/TESTS:
Removed.
tests/recompilation/test_functions:
Make sure the old result file is removed before starting
each test.
Put the mmake output for tests which are supposed to fail
into a different file for each test.
tests/warnings/Mmakefile:
Use %.c rather than $(cs_subdir)%.c in a rule.
The $(cs_subdir) part doesn't work with `mmc --make',
and isn't necessary any more (modules.m generates a rule
`module.c: $(cs_subdir)module.c').
tests/README:
Updated.
tools/bootcheck:
tools/test_mercury:
Use `mmake runtests' instead of the `runtests' script.
Add a `-f' (`--failing-tests') option to bootcheck which
runs only the failing tests from the last run.
tools/test_mercury:
tools/run_all_tests_from_cron:
Use the new framework to summarize test failures.
Estimated hours taken: 0.25
tools/run_all_tests_from_cron:
tools/test_mercury:
Set up to run the tests on mundroo (Solaris/x86 2.8).
The tests on mundroo and taifun are run 3 times a week.
Always test the main branch twice per week, rather than
just on even-numbered days.
Estimated hours taken: 0.1
tools/run_all_tests_from_cron:
tools/test_mercury:
Fix a bug in my last change which caused the nightly tests
to fail on murlibobo -- sh doesn't do tilde expansion, so
hard-code the location of the .path file..
Estimated hours taken: 0.25
tools/run_all_tests_from_cron:
For some reason hydra doesn't handle .forward files,
so mail to stayl@cs.mu.oz.au rather than stayl.
