Skip to content

Fix failing tests due to timeout because of LaTeX update breaking tufte doc #13647

@cderv

Description

@cderv

Somehow we have some failing test in some situations

running 2 tests from ./smoke/render/render-page-layout.test.ts
[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf ...'[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf' has been running for over (1m0s)
'[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf' has been running for over (2m0s)
'[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf' has been running for over (4m0s)
'[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf' has been running for over (8m0s)
 FAILED (10m0s)
[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html ...'[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html' has been running for over (1m0s)
'[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html' has been running for over (2m0s)
'[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html' has been running for over (4m0s)
'[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html' has been running for over (8m0s)
 FAILED (10m0s)
Ful log

running 2 tests from ./smoke/render/render-page-layout.test.ts
[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf ...'[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf' has been running for over (1m0s)
'[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf' has been running for over (2m0s)
'[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf' has been running for over (4m0s)
'[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf' has been running for over (8m0s)
 FAILED (10m0s)
[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html ...'[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html' has been running for over (1m0s)
'[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html' has been running for over (2m0s)
'[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html' has been running for over (4m0s)
'[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html' has been running for over (8m0s)
 FAILED (10m0s)

ERRORS 

[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf => ./test.ts:346:8
error: AssertionError: Failed assertion: 

--------------------------------------------------------------------------------
[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf
          ./run-tests.sh smoke/render/render-page-layout.test.ts

[verify] > Output Created

No output created message
AssertionError: No output created message
    at Module.assert (https://jsr.io/@std/assert/0.224.0/assert.ts:18:11)
    at assert (https://jsr.io/@std/testing/0.224.0/asserts.ts:608:11)
    at Object.verify (file:///home/runner/work/quarto-cli/quarto-cli/tests/verify.ts:316:7)
    at fn (file:///home/runner/work/quarto-cli/quarto-cli/tests/test.ts:256:25)
    at eventLoopTick (ext:core/01_core.js:218:9)
    at async innerWrapped (ext:cli/40_test.js:180:5)
    at async outerWrapped (ext:cli/40_test.js:123:14)

OUTPUT:
    - The project is out-of-sync -- use `renv::status()` for details.
    
    
    
    processing file: tufte-pdf.qmd
    
    1/29                        
    
    2/29 [fig-margin]           
    
    3/29                        
    
    4/29 [fig-fullwidth]        
    
    5/29                        
    
    6/29 [fig-main]             
    
    7/29                        
    
    8/29 [fig-main-margin-cap]  
    
    9/29                        
    
    10/29 [unnamed-chunk-1]      
    
    11/29                        
    
    12/29 [fig-two-together]     
    
    13/29                        
    
    14/29 [fig-two-separate]     
    
    15/29                        
    
    16/29 [fig-margin-together]  
    
    17/29                        
    
    18/29 [unnamed-chunk-2]      
    
    19/29                        
    
    20/29 [fig-margin-separate-a]
    
    21/29                        
    
    22/29 [unnamed-chunk-3]      
    
    23/29                        
    
    24/29 [unnamed-chunk-4]      
    
    25/29                        
    
    26/29 [unnamed-chunk-5]      
    
    27/29                        
    
    28/29 [unnamed-chunk-6]      
    
    29/29                        
    
    output file: tufte-pdf.knit.md
    
    
    pandoc 
    to: latex
    output-file: tufte-pdf.tex
    standalone: true
    pdf-engine: lualatex
    variables:
      graphics: true
      tables: true
    default-image-extension: pdf
    reference-location: margin
    
    metadata
    documentclass: scrartcl
    classoption:
      - DIV=11
      - numbers=noendperiod
    papersize: letter
    header-includes:
      - \KOMAoption{captions}{tableheading}
    block-headings: true
    title: A Quarto Page Layout Example
    subtitle: Inspired by Tufte Handout, Using Quarto
    date: today
    citation-location: margin
    bibliography:
      - skeleton.bib
    
    
    Rendering PDF
    running lualatex - 1
    timed out after 10 minutes
    
    Stack trace:
        at asErrorEx (file:///home/runner/work/quarto-cli/quarto-cli/src/core/lib/error.ts:74:12)
        at logError (file:///home/runner/work/quarto-cli/quarto-cli/src/core/log.ts:348:15)
        at fn (file:///home/runner/work/quarto-cli/quarto-cli/tests/test.ts:239:13)
        at eventLoopTick (ext:core/01_core.js:218:9)
        at async innerWrapped (ext:cli/40_test.js:180:5)
        at async outerWrapped (ext:cli/40_test.js:123:14)
    throw new AssertionError(msg);
          ^
    at assert (https://jsr.io/@std/assert/0.224.0/assert.ts:18:11)
    at Module.fail (https://jsr.io/@std/assert/0.224.0/fail.ts:17:3)
    at fail (https://jsr.io/@std/testing/0.224.0/asserts.ts:663:11)
    at fn (file:///home/runner/work/quarto-cli/quarto-cli/tests/test.ts:320:11)

[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html => ./test.ts:346:8
error: AssertionError: Failed assertion: 

--------------------------------------------------------------------------------
[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html
          ./run-tests.sh smoke/render/render-page-layout.test.ts

[verify] > Output Created

No output created message
AssertionError: No output created message
    at Module.assert (https://jsr.io/@std/assert/0.224.0/assert.ts:18:11)
    at assert (https://jsr.io/@std/testing/0.224.0/asserts.ts:608:11)
    at Object.verify (file:///home/runner/work/quarto-cli/quarto-cli/tests/verify.ts:316:7)
    at fn (file:///home/runner/work/quarto-cli/quarto-cli/tests/test.ts:256:25)
    at eventLoopTick (ext:core/01_core.js:218:9)
    at async innerWrapped (ext:cli/40_test.js:180:5)
    at async outerWrapped (ext:cli/40_test.js:123:14)

OUTPUT:
    timed out after 10 minutes
    
    Stack trace:
        at asErrorEx (file:///home/runner/work/quarto-cli/quarto-cli/src/core/lib/error.ts:74:12)
        at logError (file:///home/runner/work/quarto-cli/quarto-cli/src/core/log.ts:348:15)
        at fn (file:///home/runner/work/quarto-cli/quarto-cli/tests/test.ts:239:13)
        at eventLoopTick (ext:core/01_core.js:218:9)
        at async innerWrapped (ext:cli/40_test.js:180:5)
        at async outerWrapped (ext:cli/40_test.js:123:14)
    throw new AssertionError(msg);
          ^
    at assert (https://jsr.io/@std/assert/0.224.0/assert.ts:18:11)
    at Module.fail (https://jsr.io/@std/assert/0.224.0/fail.ts:17:3)
    at fail (https://jsr.io/@std/testing/0.224.0/asserts.ts:663:11)
    at fn (file:///home/runner/work/quarto-cli/quarto-cli/tests/test.ts:320:11)

 FAILURES 

[smoke] > quarto render docs/page-layout/tufte-pdf.qmd --to pdf => ./test.ts:346:8
[smoke] > quarto render docs/page-layout/tufte-html.qmd --to html => ./test.ts:346:8

FAILED | 0 passed | 2 failed (20m0s)

This is due to timeout and it makes our CI fail but no always/

Locally documents renders fine and test seems to ./smoke/render/render-page-layout.test.ts at least on windows.

Investigation required.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions