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

CI logs do not report testset stats for tests run on node 1 #20362

Open
amitmurthy opened this issue Feb 1, 2017 · 4 comments
Open

CI logs do not report testset stats for tests run on node 1 #20362

amitmurthy opened this issue Feb 1, 2017 · 4 comments
Labels
bug Indicates an unexpected problem or unintended behavior priority This should be addressed urgently testsystem The unit testing framework and Test stdlib

Comments

@amitmurthy
Copy link
Contributor

amitmurthy commented Feb 1, 2017

Noticed this on both Travis and AV.

The output does not include testset stats for compile and parallel though both appear to have been run considering the line From worker 1: From worker 1:

channels (15)             |   11.70  |  0.48  |  4.1 | 318.54     | 745.59  
fft (16)                  |   38.16  |  0.54  |  1.4 | 673.49     | 384.01  
dsp (16)                  |   13.64  |  0.15  |  1.1 | 227.76     | 404.87  
examples (16)             |   22.79  |  0.50  |  2.2 | 543.03     | 500.16  
cmdlineargs (14)          |  158.12  |  0.00  |  0.0 | 51.02      | 475.30  
	From worker 1:		From worker 1:	
Test Summary: |     Pass  Broken     Total
  Overall     | 20830691     617  20831308
    SUCCESS
@amitmurthy amitmurthy added the testsystem The unit testing framework and Test stdlib label Feb 1, 2017
@kshyatt
Copy link
Contributor

kshyatt commented Feb 1, 2017

I think I had a fix for this as part of #19567 if anyone wants to snipe it.

@StefanKarpinski StefanKarpinski added the priority This should be addressed urgently label Feb 2, 2017
@amitmurthy
Copy link
Contributor Author

amitmurthy commented May 22, 2017

Under certain circumstances failures in distributed tests do not trigger a CI failure, Example - https://travis-ci.org/JuliaLang/julia/jobs/234585324 . I have seen distributed tests failing under CI recently so it is not always the case.

@amitmurthy
Copy link
Contributor Author

Ignore the above comment. While the lack of display testset stats is indeed an issue, not triggering CI failure is an issue in the test script.

@JeffBezanson JeffBezanson added the bug Indicates an unexpected problem or unintended behavior label Sep 24, 2017
@PallHaraldsson
Copy link
Contributor

PallHaraldsson commented Nov 17, 2023

Noticed this on both Travis and AV.

Aren't those outdated CI systems? Is this a problem for the current Julia CI system? I'm curious if this
is still a priority for at least JuliaLang/julia? If not should the issue be closed? I was looking into the 3 "priority" open issues, 2 of still from 2017... Does the issue at least need to be open for users of those old CI systems, but possibly not marked priority?

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior priority This should be addressed urgently testsystem The unit testing framework and Test stdlib
Projects
None yet
Development

No branches or pull requests

5 participants