Test suite graphviz-testsuite: RUNNING...
This is the test suite for the graphviz library.
If any of these tests fail, please inform the maintainer,
including full output of this test suite.
======================================================================
Running test: "Printing and parsing of Attributes".
The most common source of errors in printing and parsing are for
Attributes.
+++ OK, passed 200 tests.
All tests for "Printing and parsing of Attributes" were successful!
======================================================================
Running test: "Printing generalised Dot code".
When generalising "DotGraph" values to other "DotRepr" values,
the generated Dot code should be identical.
+++ OK, passed 200 tests.
All tests for "Printing generalised Dot code" were successful!
======================================================================
Running test: "Printing and Parsing DotReprs".
The graphviz library should be able to parse back in its own
generated Dot code for any "DotRepr" instance
+++ OK, passed 200 tests.
+++ OK, passed 200 tests.
+++ OK, passed 200 tests.
All tests for "Printing and Parsing DotReprs" were successful!
======================================================================
Running test: "Pre-processing Dot code".
When parsing Dot code, some pre-processing is done to remove items
such as comments and to join together multi-line strings. This
test verifies that this pre-processing doesn't affect actual
Dot code by running the pre-processor on generated Dot code.
This test is not run on generalised Dot graphs as if it works for
normal dot graphs then it should also work for generalised ones.
+++ OK, passed 200 tests.
All tests for "Pre-processing Dot code" were successful!
======================================================================
Running test: "Augmenting FGL Graphs".
The various Graph to Graph functions in Data.GraphViz should
only _augment_ the graph labels and not change the graphs
themselves. This test compares the original graphs to these
augmented graphs and verifies that they are the same.
*** Failed! (after 1 test):
Exception:
Error running utility program: Error messages from neato:
-1:']'->[]
The tests for "Augmenting FGL Graphs" failed!
Not attempting any further tests.
Test suite graphviz-testsuite: FAIL
Test suite logged to: dist/test/graphviz-2999.16.0.0-graphviz-testsuite.log
0 of 1 test suites (0 of 1 test cases) passed.
- generic-deriving: updated to version 1.2.1
- ghc-mod: updated to version 1.10.17
- gitit: updated to version 0.10.0.1
- graphviz: updated to version 2999.13.0.3
- hsemail: updated to version 1.7.2
- split: updated to version 0.1.4.3
svn path=/nixpkgs/trunk/; revision=34384
- authenticate: updated to version 1.2.1.1
- blaze-html: added version 0.5.0.0 (unused right now because happstack can't deal with it)
- BNFC-meta: updated to version 0.3.0.2
- graphviz: patched build to succeed with transformers 0.3.x
- haskeline: updated to version 0.6.4.7
- http-conduit: updated to version 1.4.1.3
- numeric-prelude: updated to version 0.3.0.2
- pandoc: updated to version 1.9.3
svn path=/nixpkgs/trunk/; revision=34087
- authenticate: updated to version 1.2.1
- blaze-builder-enumerator: updated to version 0.2.0.4
- graphviz: updated to version 2999.13.0.2
- tls: updated to version 0.9.4
svn path=/nixpkgs/trunk/; revision=33853
By now, it happened twice that a commit broke GHC and thus all Haskell packages
we have in Nixpkgs. On such an occasion, I receive well in excess of 3000
notification e-mails from Hydra, and then I receive another 3000 e-mails after
the bug has been fixed. Under these circumstances, subscribing to these
notifications makes no sense for me.
svn path=/nixpkgs/trunk/; revision=33392
This update obsoletes the requirement for polyparse 1.4, which has
subsequently been removed from the repository.
svn path=/nixpkgs/trunk/; revision=28629
The new files ...
* conform to the coding guidelines,
* consistently specify meta.maintainers and meta.platforms,
* have proper descriptions and licenses as specified in their Cabal file, and
* take advantage of the new cabal.nix extensions, i.e. proper
distinction between buildInputs and propagatedBuildInputs.
Furthermore, the following updates were performed:
* haskell-Ranged-sets: updated to version 0.3.0
* haskell-Shellac-haskeline: updated to version 0.2.0.1
* haskell-cpphs: updated to version 1.12
* haskell-hslogger: updated to version 1.1.5
* haskell-xml: updated to version 1.3.9
* haskell-HDBC-postgresql: updated to version 2.3.2.0
* haskell-HDBC-sqlite3: updated to version 2.3.3.0
* haskell-HDBC: updated to version 2.3.1.0
* haskell-base-unicode-symbols: updated to version 0.2.2.1
* haskell-convertible: updated to version 1.0.11.0
* haskell-monad-control: updated to version 0.2.0.2
* haskell-murmur-hash: updated to version 0.1.0.4
* haskell-repa: updated to version 2.1.1.3
* haskell-statistics: updated to version 0.9.0.0
* haskell-ansi-terminal: updated to version 0.5.5
haskell-maybench was dropped, because it cannot be built with recent
versions of Cabal:
Configuring maybench-0.2.4.1...
Setup: At least the following dependencies are missing:
Cabal >=1.2 && <1.5
svn path=/nixpkgs/trunk/; revision=28446
