| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Reduce the timeout to 30 minutes for all the jobs, since it is enough.
Set strategy.fail-fast to false, so that we can see the full logs.
|
|
Replacing Python-Tools with Zig-Tools
|
|
Version number added.
|
|
|
|
Added a loop for the formatting test, so we can see where errors happen.
|
|
|
|
|
|
Improve ci more
|
|
More improvements
|
|
|
|
Remove support for old .h, .cpp and .bat files.
Set eol mode to lf for Python scripts.
Closes #252
|
|
Add the zig-out directory, since the install step is available.
Remove the vim backup and swap files, since it is possible to configure
vim to use a custom directory.
Ensure all the directories are anchored to the root directory.
Closes #251
|
|
Add a job to run the ziglings unit tests, using `zig build test`.
|
|
Use the new version of actions/checkout, since all Github Actions will
begin running on Node16 instead of Node12.
See https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.
|
|
The non-conforming formatting was not detected by the eowyn.sh script,
due to a bug.
|
|
Currently, `zig fmt` exit status is ignored, making it useless.
Ensure that the script terminates early if there is an error.
Print a message to stdout before executing `zig fmt`, in order to make
the possible error more visible.
|
|
Quote all the variables, even though we know that it is safe.
Fix coding style.
|
|
|
|
Improve test coverage
|
|
|
|
Add a test for `zig build -Dn=1` in order to test that a broken exercise
will print an hint.
|
|
In test case 1 and 2, move the -Dhealed option before the -Dn option,
for consistency.
Fix a typo in cmd.setName in test case 1 and 2.
Remove a confusing comment in test case 1.
|
|
Add tests for `zig build` and `zig build -Dn=1 start`, in order to test
that the all the exercises are processed in the correct order.
|
|
Currently, ZiglingStep prints the raw exercise output. This is not a
problem when executing `zig build` from the shell, but in a unit test it
is necessary to know when the exercise output ends.
Document that Exercise.output should not have trailing whitespace.
Ensure this is true by adding a check in the validate_exercises
function.
Remove trailing whitespace in exercises 68 and 99.
Simplify the output validation in ZiglingStep.makeInternal.
Checking that the length of the actual and expected output is the same
is not necessary, since trailing whitespace has been removed. Simply do
an exact comparison.
Print the trimmed exercise output, instead of the raw output.
This will ensure that the exercise output always ends with only one LF
character.
Fix some small coding style issues.
|
|
The current cleanup code is incorrect, since it may delete the healed
directory while one test case is running.
The solution is to make each test case isolate, with its own setup and
teardown. Unfortunately it is currently not possible, since each test
case modify the same directory.
Disable the cleanup step, until a better solution is found.
|
|
Currently, if there is an error when creating the patches/healed
directory, the error message will be printed on stderr, but the build
runner will report the test as being successful.
Add the fail function and the FailStep, so that the error will be
correctly handled by the build runner.
Remove the PatchStep, and instead add the heal function so that all the
exercises are healed before starting the tests.
The heal function executes at the configuration phase, but the possible
error is handled by the build runner.
|
|
I still had C interop under stdlib, which it isn't.
|
|
|
|
|
|
|
|
typo fixed
|
|
added first formatting exercise
|
|
|
|
Improve CI
|
|
Add the update-patches.py tool.
Update all the patches, so that the files are up-to-date and use the
same patch file format.
|
|
Update the eowyn.sh script to check the healed exercises formatting,
before running `zig build`.
|
|
Add the check-exercises.py tool in the new tools directory. It is used
to check that the exercises are correctly formatted, printing on stderr
the invalid ones and the diff in the unified format.
Update the exercises that don't use the canonical zig fmt format.
Update some patches that cause the generated zig file to be incorrectly
formatted.
|
|
Add a new github workflow named CI.
Add a job named compat, checking that and old Zig compiler will not fail
with a compiler error, but instead will print an useful error message.
|
|
build: restore compatibility with old Zig compilers
|
|
In same cases, the progress messages from the compiler are intermixed
with the messages printed by ZiglingStep.
This intermixing appears in two cases:
- when printing, e.g., the message "Checking 0_arrays2.zig..."
- when printing the compiler errors
Closes #230
|
|
Move the code for printing compiler errors and messages to the new
ZiglingStep.printErrors method.
Call printErrors in the Zigling.doCompile method, both in the normal and
error flow.
When handling an error from the Zig IPC, add the case when the compiler
was unable to return the executable path.
Before using the IPC, the error was
"The following command exited with error code 1"
now it is
"The following command failed to communicate the compilation result"
|
|
Commit e214c44 (build: update ZiglingStep to the new API) broke again
the compatibility support for old compilers, due to the use of the
multi-object for loop syntax.
Move the Zig IPC support code to src/ipc.zig.
Use the while statement, instead of the for statement.
|
|
Update ZiglingStep
|
|
Update the code to the breaking change in ziglang
commit c96cb98ad (CLI: remove --enable-cache option).
Replace the --enable-cache option with the --listen=- option and use the
Zig IPC to get the path to the executable.
Closes #236
|
|
The special case was added because it was used by the Eowyn github
workflow.
As a side effect, however, it prevents testing the normal case used by
users.
Disable it, until a better solution is found.
|
|
|
|
added cname
|
|
|
|
|
