Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test suite failure for package mmark-0.0.7.2 #76

Closed
Tracked by #316
juhp opened this issue Feb 22, 2021 · 2 comments · Fixed by #77
Closed
Tracked by #316

Test suite failure for package mmark-0.0.7.2 #76

juhp opened this issue Feb 22, 2021 · 2 comments · Fixed by #77

Comments

@juhp
Copy link

juhp commented Feb 22, 2021

In the Stackage Nightly build:

    Failures:
    
      tests/Text/MMark/TestUtils.hs:113:22: 
      1) parse and render, 6.1 Blackslash escapes, CM297
           expected: "<p><a href=\"http://example.com/?find=*\">http://example.com/?find=*</a></p>\n"
            but got: "<p><a href=\"http://example.com?find=*\">http://example.com?find=*</a></p>\n"
    
      To rerun use: --match "/parse and render/6.1 Blackslash escapes/CM297/"
    
      tests/Text/MMark/TestUtils.hs:113:22: 
      2) parse and render, 6.5 Links, CM472
           expected: "<p><a href=\"#fragment\">link</a></p>\n<p><a href=\"http://example.com/#fragment\">link</a></p>\n<p><a href=\"
http://example.com/?foo=3#frag\">link</a></p>\n"
            but got: "<p><a href=\"#fragment\">link</a></p>\n<p><a href=\"http://example.com#fragment\">link</a></p>\n<p><a href=\"h
ttp://example.com?foo=3#frag\">link</a></p>\n"
    
      To rerun use: --match "/parse and render/6.5 Links/CM472/"
    
      tests/Text/MMark/TestUtils.hs:113:22: 
      3) parse and render, 6.7 Autolinks, CM565
           expected: "<p><a href=\"http://foo.bar.baz/\">http://foo.bar.baz/</a></p>\n"
            but got: "<p><a href=\"http://foo.bar.baz\">http://foo.bar.baz</a></p>\n"
    
      To rerun use: --match "/parse and render/6.7 Autolinks/CM565/"
    
      tests/Text/MMark/TestUtils.hs:113:22: 
      4) parse and render, 6.7 Autolinks, CM571
           expected: "<p><a href=\"http://../\">http://../</a></p>\n"
            but got: "<p><a href=\"http://..\">http://..</a></p>\n"
    
      To rerun use: --match "/parse and render/6.7 Autolinks/CM571/"
    
      tests/Text/MMark/TestUtils.hs:113:22: 
      5) parse and render, given a complete, comprehensive document, outputs expected the HTML fragment
           expected: "<h1 id=\"lorem-ipsum\">Lorem ipsum</h1>\n<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer varius mi\norci, rhoncus ornare nunc tincidunt nec. Aliquam cursus posuere ornare.\nQuisque posuere euismod nunc, sed pellentesque metus hendrerit eu. Donec\nscelerisque accumsan ante quis interdum. Nullam nec mauris dolor. Lorem\nipsum dolor sit amet, consectetur adipiscing elit. Phasellus id porttitor\nnunc, sed laoreet eros. Maecenas ipsum ex, sagittis ut quam quis, vehicula\nfringilla tortor. Vestibulum quis consequat mauris, sed porta risus.\nVestibulum nec ornare leo. Cras pharetra, ex sed dapibus pretium, diam\nlectus accumsan enim, at malesuada tellus lorem et orci. Sed condimentum\nvarius ex in mollis.</p>\n<p><a href=\"https://example.org/\">https://example.org/</a></p>\n<p>Ut in imperdiet neque. Etiam iaculis rhoncus nisl vel porta. Praesent velit\norci, laoreet suscipit...
:
@mrkkrp
Copy link
Member

mrkkrp commented Feb 22, 2021

Why did you add it to expected benchmark failures though? Shouldn't it be in expected test failures?

@juhp
Copy link
Author

juhp commented Feb 23, 2021

Because I was tired, good catch :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants