I'm not sure whether this was by intention, but so far postPatch hooks were
silently skipped whenever the patches list was empty. This change could possibly
change the build results of the following packages:
* gcc
* cmake (264)
* systemtap
* quemu-kvm
These packages all have in common that they have a postPatch hook and the
patches list can be empty when certain conditions are met.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
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.
Running 4 test suites...
Test suite doctests: RUNNING...
### Error in src/Data/Complex/Lens.hs:33: expression `let { a doctests: <stderr>: hPutChar: invalid argument (invalid character)
Test suite doctests: FAIL
Test suite logged to: dist/test/lens-3.8.7.3-doctests.log
Test suite hunit: RUNNING...
Test suite hunit: PASS
Test suite logged to: dist/test/lens-3.8.7.3-hunit.log
Test suite properties: RUNNING...
Test suite properties: PASS
Test suite logged to: dist/test/lens-3.8.7.3-properties.log
Test suite templates: RUNNING...
Test suite templates: PASS
Test suite logged to: dist/test/lens-3.8.7.3-templates.log
3 of 4 test suites (3 of 4 test cases) passed.
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.
Running 4 test suites...
Test suite doctests: RUNNING...
### Error in src/Data/Complex/Lens.hs:33: expression `let { a doctests: <stderr>: hPutChar: invalid argument (invalid character)
Test suite doctests: FAIL
Test suite logged to: dist/test/lens-3.8.7.3-doctests.log
Test suite hunit: RUNNING...
Test suite hunit: PASS
Test suite logged to: dist/test/lens-3.8.7.3-hunit.log
Test suite properties: RUNNING...
Test suite properties: PASS
Test suite logged to: dist/test/lens-3.8.7.3-properties.log
Test suite templates: RUNNING...
Test suite templates: PASS
Test suite logged to: dist/test/lens-3.8.7.3-templates.log
3 of 4 test suites (3 of 4 test cases) passed.
Test suite test: RUNNING...
test: SqlError {sqlState = "", sqlNativeError = -1, sqlErrorMsg = "could not connect to server: No such file or directory\n\tIs the server running locally and accepting\n\tconnections on Unix domain socket \"/tmp/.s.PGSQL.5432\"?\n"}
Test suite test: FAIL
Test suite logged to: dist/test/postgresql-simple-0.2.4.1-test.log
0 of 1 test suites (0 of 1 test cases) passed.
tests/Test.hs:3:8:
Could not find module `Happstack.Server.Tests'
Perhaps you meant
Happstack.Server.Types (from happstack-server-7.1.6)
Happstack.Server.Auth (from happstack-server-7.1.6)
Happstack.Server.Client (from happstack-server-7.1.6)
Use -v to see a list of the files searched for.
