- Nov 09, 2019
-
-
It was previously marked as broken due to #12236 however it passes for me locally while failing on CI.
-
Due to #17447.
-
<Rts.h> must always come first.
-
While linking is still slow (#16084) all of the correctness issues which were preventing us from being able to enforce testsuite-green on Windows are now resolved.
-
This test uses -dynamic-too, which is not supported on Windows.
-
The event manager is not supported on Windows.
-
This was a regression introduced with the Path refactoring.
-
[ci-skip]
-
-
-
See #16180.
-
- Nov 08, 2019
-
-
Marks executeFile001 as broken in all concurrent ways.
-
-
-
When floating a single-alternative case we previously would set the context level to the level where we were floating the case. However, this is wrong as we are only moving the case and its binders. This resulted in #16978, where the disrepancy caused us to unnecessarily abstract over some free variables of the case body, resulting in shadowing and consequently Core Lint failures. (cherry picked from commit a2a0e6f3bb2d02a9347dec4c7c4f6d4480bc2421)
-
This took a bit of trial-and-error to get working so it seems worth having in the tree.
-
-
Some tests depend on the RTS linker. Introduce a modifier to skip such tests, in case the RTS linker is not available.
-
Otherwise this fails on Windows.
-
The Windows build seems to be stricter about not providing threading primitives in the non-threaded RTS.
-
-
I have no idea why I marked this as inline originally but clearly it shouldn't be inlined.
-
In general this is the convention that we use in the RTS. On Windows things actually fail if we break it. For instance, you see things like: includes\stg\Types.h:26:9: error: warning: #warning "Mismatch between __USE_MINGW_ANSI_STDIO definitions. If using Rts.h make sure it is the first header included." [-Wcpp] -
An inconsistency in the name of m32_allocator_flush caused the build to fail with a missing prototype error.
-
-
This should fix the #17108 and #17249 with the fix from https://github.com/haskell/process/pull/159.
-
Before this patch, Hadrian didn't care about the TEST_ENV and METRICS_FILE environment variables, that the performance testing infrastructure uses to record perf tests results from CI jobs. It now looks them up right before running the testsuite driver, and passes suitable --test-env/--metrics-file arguments when these environment variables are set.
-
- Nov 07, 2019
-
-
If sphinx's python version check failed, many people prefer to build without documents instead of stopping on the error. So this commit fixes the following: * Modify AC_MSG_ERROR to AC_MSG_WARN * Add clearing of SPHINXBUILD variable when check fails See also !2016.
-
-
These affect output and therefore should be part of the flag hash.
-
For s390x the GHC calling convention is only supported since LLVM version 10. Issue a warning in case an older version of LLVM is used.
-
!1906 left some loose ends in regards to Template Haskell's treatment of unary tuples. This patch ends to tie up those loose ends: * In addition to having `TupleT 1` produce unary tuples, `TupE [exp]` and `TupP [pat]` also now produce unary tuples. * I have added various special cases in GHC's pretty-printers to ensure that explicit 1-tuples are printed using the `Unit` type. See `testsuite/tests/th/T17380`. * The GHC 8.10.1 release notes entry has been tidied up a little. Fixes #16881. Fixes #17371. Fixes #17380.
-
- Nov 06, 2019
-
-
-
This checks the configuration about python3-sphinx. We need python3-sphinx instead of python2-sphinx to build documentation. The approach is as follows: * Check python3 version with custom `conf.py` invoked from sphinx-build` executable * Place custom `conf.py` into new `utils/check-sphinx` directory If sphinx is for python2 not python3, it's treated as config ERROR instead of WARN. See also #17346 and #17356.
-
Fixing #17255.
-
These are now handled in the cabal file's include-dirs field.
-
- Nov 05, 2019
-
-
-
-
-
We can handle non-void constraints since !1733, so we can now express the strictness of `-XEmptyCase` just by adding a non-void constraint to the initial Uncovered set. For `case x of {}` we thus check that the Uncovered set `{ x | x /~ ⊥ }` is non-empty. This is conceptually simpler than the plan outlined in #17376, because it talks to the oracle directly. In order for this patch to pass the testsuite, I had to fix handling of newtypes in the pattern-match checker (#17248). Since we use a different code path (well, the main code path) for `-XEmptyCase` now, we apparently also handle #13717 correctly. There's also some dead code that we can get rid off now. `provideEvidence` has been updated to provide output more in line with the old logic, which used `inhabitationCandidates` under the hood. A consequence of the shift away from the `UncoveredPatterns` type is that we don't report reduced type families for empty case matches, because the pretty printer is pure and only knows the match variable's type. Fixes #13717, #17248, #17386
-
