Styjun

'spazieren' - walking in a silly and affected manner?

Does the telecom provider need physical access to the SIM card to clone it?

Correct way of simplifying the result of an integral

Why does the U.S. military maintain their own weather satellites?

"Practice makes perfect" and "c'est en forgeant qu'on devient forgeron"

How can I store milk for long periods of time?

An alternative to "two column" geometry proofs

Turn off Google Chrome's Notification for "Flash Player will no longer be supported after December 2020."

New coworker has strange workplace requirements - how should I deal with them?

Blender - Alpha is Luminance equivalent

Is it good practice to speed up and slow down where not written in a song?

Could a simple hospital oxygen mask protect from aerosol poison?

How to run a command 1 out of N times in Bash

Is the equational theory of groups axiomatized by the associative law?

Why do motor drives have multiple bus capacitors of small value capacitance instead of a single bus capacitor of large value?

How can an F-22 Raptor reach supersonic speeds without having supersonic inlets?

German equivalent to "going down the rabbit hole"

Ways you can end up paying interest on a credit card if you pay the full amount back in due time

Why didn't Thatcher give Hong Kong to Taiwan?

Pandas transform inconsistent behavior for list

How can I improve my formal definitions?

How do you manage to study and have a balance in your life at the same time?

Can a human variant take proficiency in initiative?

Are there consequences for not filing a DMCA (any country)

How to fix the following warning: `WARN: The resource for '' is not found, drilling down to the details of this test won't be possible.`

“Resource not found” trying to add junit tests into sonarqubeSonarQube Component Coverage details with JUnitTest reports: How to avoid resource not found warning?Class not found: javax.annotation and Resource not found: <java Test Classes> while running gradle buildHow to fix the following issue, plotting a keras model?How does the Sonarqube Gradle Plugin locate test resourcesHow to ignore the 'not covered by tests' warning?How to get details page and follow the links with Scrapy?How to scrap all the test match details in cricinfohow to fix :unsatisfiableerror: the following specifications were found to be in conflictSonarqube for python: Test success score not being discovered - The resource for 'tests.test_transformation_helper.TestCase' is not found

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

1

1

My abridged sonar-project.properties files is as follows:

# Sources
sonar.sources=felix
sonar.sources.inclusions=**/**.py
sonar.exclusions=**/test_*.py,**/**.pyc,felix/utils/*,**/*.iml

# Linter
sonar.python.pylint=/usr/local/bin/pylint
sonar.python.pylint_config=.pylintrc
sonar.python.pylint.reportPath=pylint-report.txt

# Coverage / Unit Tests
sonar.tests=./tests
sonar.test.inclusions=**/test_**.py
sonar.python.xunit.skipDetails=false
#DEFAULT VALUES: sonar.python.xunit.reportPath=xunit-reports/xunit-result-*.xml
#DEFAULT VALUES: sonar.python.coverage.reportPath=coverage-reports/*coverage-*.xml

The abridged source code tree is like so:

├── felix
│ ├── __init__.py
│ ├── __pycache__
│ │ ├── __init__.cpython-35.pyc
│ │ ├── process.cpython-35.pyc
│ │ └── spark.cpython-35.pyc
│ ├── felix.iml
│ ├── process.py
│ ├── spark.py
│ └── utils
│ └── utils.py
├── requirements.txt
├── setup.py
├── sonar-project.properties
├── tests
│ ├── __init__.py
│ ├── __pycache__
│ │ ├── __init__.cpython-35.pyc
│ │ └── test_process.cpython-35-PYTEST.pyc
│ ├── cia-spark.iml
│ ├── data
│ └── test_process.py
└── tox.ini

I'm getting the following warning, though, when I run the sonar-scanner: WARN: The resource for '' is not found, drilling down to the details of this test won't be possible

Could someone, please, let me know why I'm getting this warning and how can I get rid of / fix it? Thanks.

python-3.x sonarqube sonarqube-scan

share|improve this question

edited Apr 30 at 21:46

Lev

asked Mar 28 at 0:29

LevLev

2666 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Here is the line before the warning line: INFO: Processing report '/root/jenkins/workspace/CIA_Cloud_Insights_cia-spark_dev/xunit-reports/xunit-result-tests.xml' Could it be that it's stumbling over a newly created folder and I just need to exclude it, may be?
  
  – Lev
  Apr 29 at 20:38
  
  

  
  
  
  

add a comment | 

1

1

My abridged sonar-project.properties files is as follows:

# Sources
sonar.sources=felix
sonar.sources.inclusions=**/**.py
sonar.exclusions=**/test_*.py,**/**.pyc,felix/utils/*,**/*.iml

# Linter
sonar.python.pylint=/usr/local/bin/pylint
sonar.python.pylint_config=.pylintrc
sonar.python.pylint.reportPath=pylint-report.txt

# Coverage / Unit Tests
sonar.tests=./tests
sonar.test.inclusions=**/test_**.py
sonar.python.xunit.skipDetails=false
#DEFAULT VALUES: sonar.python.xunit.reportPath=xunit-reports/xunit-result-*.xml
#DEFAULT VALUES: sonar.python.coverage.reportPath=coverage-reports/*coverage-*.xml

The abridged source code tree is like so:

├── felix
│ ├── __init__.py
│ ├── __pycache__
│ │ ├── __init__.cpython-35.pyc
│ │ ├── process.cpython-35.pyc
│ │ └── spark.cpython-35.pyc
│ ├── felix.iml
│ ├── process.py
│ ├── spark.py
│ └── utils
│ └── utils.py
├── requirements.txt
├── setup.py
├── sonar-project.properties
├── tests
│ ├── __init__.py
│ ├── __pycache__
│ │ ├── __init__.cpython-35.pyc
│ │ └── test_process.cpython-35-PYTEST.pyc
│ ├── cia-spark.iml
│ ├── data
│ └── test_process.py
└── tox.ini

I'm getting the following warning, though, when I run the sonar-scanner: WARN: The resource for '' is not found, drilling down to the details of this test won't be possible

Could someone, please, let me know why I'm getting this warning and how can I get rid of / fix it? Thanks.

python-3.x sonarqube sonarqube-scan

share|improve this question

edited Apr 30 at 21:46

Lev

asked Mar 28 at 0:29

LevLev

2666 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Here is the line before the warning line: INFO: Processing report '/root/jenkins/workspace/CIA_Cloud_Insights_cia-spark_dev/xunit-reports/xunit-result-tests.xml' Could it be that it's stumbling over a newly created folder and I just need to exclude it, may be?
  
  – Lev
  Apr 29 at 20:38
  
  

  
  
  
  

add a comment | 

My abridged sonar-project.properties files is as follows:

# Sources
sonar.sources=felix
sonar.sources.inclusions=**/**.py
sonar.exclusions=**/test_*.py,**/**.pyc,felix/utils/*,**/*.iml

# Linter
sonar.python.pylint=/usr/local/bin/pylint
sonar.python.pylint_config=.pylintrc
sonar.python.pylint.reportPath=pylint-report.txt

# Coverage / Unit Tests
sonar.tests=./tests
sonar.test.inclusions=**/test_**.py
sonar.python.xunit.skipDetails=false
#DEFAULT VALUES: sonar.python.xunit.reportPath=xunit-reports/xunit-result-*.xml
#DEFAULT VALUES: sonar.python.coverage.reportPath=coverage-reports/*coverage-*.xml

The abridged source code tree is like so:

├── felix
│ ├── __init__.py
│ ├── __pycache__
│ │ ├── __init__.cpython-35.pyc
│ │ ├── process.cpython-35.pyc
│ │ └── spark.cpython-35.pyc
│ ├── felix.iml
│ ├── process.py
│ ├── spark.py
│ └── utils
│ └── utils.py
├── requirements.txt
├── setup.py
├── sonar-project.properties
├── tests
│ ├── __init__.py
│ ├── __pycache__
│ │ ├── __init__.cpython-35.pyc
│ │ └── test_process.cpython-35-PYTEST.pyc
│ ├── cia-spark.iml
│ ├── data
│ └── test_process.py
└── tox.ini

I'm getting the following warning, though, when I run the sonar-scanner: WARN: The resource for '' is not found, drilling down to the details of this test won't be possible

Could someone, please, let me know why I'm getting this warning and how can I get rid of / fix it? Thanks.

python-3.x sonarqube sonarqube-scan

share|improve this question

edited Apr 30 at 21:46

Lev

asked Mar 28 at 0:29

LevLev

2666 bronze badges

# Sources
sonar.sources=felix
sonar.sources.inclusions=**/**.py
sonar.exclusions=**/test_*.py,**/**.pyc,felix/utils/*,**/*.iml

# Linter
sonar.python.pylint=/usr/local/bin/pylint
sonar.python.pylint_config=.pylintrc
sonar.python.pylint.reportPath=pylint-report.txt

# Coverage / Unit Tests
sonar.tests=./tests
sonar.test.inclusions=**/test_**.py
sonar.python.xunit.skipDetails=false
#DEFAULT VALUES: sonar.python.xunit.reportPath=xunit-reports/xunit-result-*.xml
#DEFAULT VALUES: sonar.python.coverage.reportPath=coverage-reports/*coverage-*.xml

├── felix
│ ├── __init__.py
│ ├── __pycache__
│ │ ├── __init__.cpython-35.pyc
│ │ ├── process.cpython-35.pyc
│ │ └── spark.cpython-35.pyc
│ ├── felix.iml
│ ├── process.py
│ ├── spark.py
│ └── utils
│ └── utils.py
├── requirements.txt
├── setup.py
├── sonar-project.properties
├── tests
│ ├── __init__.py
│ ├── __pycache__
│ │ ├── __init__.cpython-35.pyc
│ │ └── test_process.cpython-35-PYTEST.pyc
│ ├── cia-spark.iml
│ ├── data
│ └── test_process.py
└── tox.ini

share|improve this question

edited Apr 30 at 21:46

Lev

asked Mar 28 at 0:29

LevLev

2666 bronze badges

share|improve this question

edited Apr 30 at 21:46

Lev

asked Mar 28 at 0:29

LevLev

2666 bronze badges

asked Mar 28 at 0:29

LevLev

2666 bronze badges

asked Mar 28 at 0:29

LevLev

2666 bronze badges

2 Answers
2

active

oldest

votes

2

I received this warning because I was excluding test files from analysis. I see than in your properties you are excluding your tests as well:

sonar.exclusions=**/test_*.py,**/**.pyc,felix/utils/*,**/*.iml

This will prevent sonar from calculating the number of tests and their pass/fail status as shown in the open source here

share|improve this answer

answered Apr 9 at 1:35

MezjMezj

4133 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for your comment, I will try removing tests from the exclusions of the main sonar sources spec and see how it behaves, then report back.
  
  – Lev
  Apr 9 at 21:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Well, removing the **/test_*.py part from sonar.exclusions did not help with eliminating that warning... In fact, these tests are still listed as excluded, I think, because they are included in the coverage part...
  
  – Lev
  Apr 29 at 20:37
  
  

  
  
  
  

add a comment | 

0

The issue turned out to be with the Pylint integrated into the Pytest call.
The parent Pytest call generated a unit testing report, which had empty classnames for additional "empty" tests that Pylint came up with.
SonarQube warned about those empty classnames.
I ended up removing Pylint Pytest integration and just running Pylint as a separate step from Pytest.

share|improve this answer

answered Apr 30 at 21:59

LevLev

2666 bronze badges

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55388461%2fhow-to-fix-the-following-warning-warn-the-resource-for-is-not-found-drill%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

2

I received this warning because I was excluding test files from analysis. I see than in your properties you are excluding your tests as well:

sonar.exclusions=**/test_*.py,**/**.pyc,felix/utils/*,**/*.iml

This will prevent sonar from calculating the number of tests and their pass/fail status as shown in the open source here

share|improve this answer

answered Apr 9 at 1:35

MezjMezj

4133 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for your comment, I will try removing tests from the exclusions of the main sonar sources spec and see how it behaves, then report back.
  
  – Lev
  Apr 9 at 21:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Well, removing the **/test_*.py part from sonar.exclusions did not help with eliminating that warning... In fact, these tests are still listed as excluded, I think, because they are included in the coverage part...
  
  – Lev
  Apr 29 at 20:37
  
  

  
  
  
  

add a comment | 

2

I received this warning because I was excluding test files from analysis. I see than in your properties you are excluding your tests as well:

sonar.exclusions=**/test_*.py,**/**.pyc,felix/utils/*,**/*.iml

This will prevent sonar from calculating the number of tests and their pass/fail status as shown in the open source here

share|improve this answer

answered Apr 9 at 1:35

MezjMezj

4133 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for your comment, I will try removing tests from the exclusions of the main sonar sources spec and see how it behaves, then report back.
  
  – Lev
  Apr 9 at 21:23
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Well, removing the **/test_*.py part from sonar.exclusions did not help with eliminating that warning... In fact, these tests are still listed as excluded, I think, because they are included in the coverage part...
  
  – Lev
  Apr 29 at 20:37
  
  

  
  
  
  

add a comment | 

I received this warning because I was excluding test files from analysis. I see than in your properties you are excluding your tests as well:

sonar.exclusions=**/test_*.py,**/**.pyc,felix/utils/*,**/*.iml

This will prevent sonar from calculating the number of tests and their pass/fail status as shown in the open source here

share|improve this answer

answered Apr 9 at 1:35

MezjMezj

4133 bronze badges

share|improve this answer

answered Apr 9 at 1:35

MezjMezj

4133 bronze badges

answered Apr 9 at 1:35

MezjMezj

4133 bronze badges

answered Apr 9 at 1:35

MezjMezj

4133 bronze badges

0

The issue turned out to be with the Pylint integrated into the Pytest call.
The parent Pytest call generated a unit testing report, which had empty classnames for additional "empty" tests that Pylint came up with.
SonarQube warned about those empty classnames.
I ended up removing Pylint Pytest integration and just running Pylint as a separate step from Pytest.

share|improve this answer

answered Apr 30 at 21:59

LevLev

2666 bronze badges

add a comment | 

0

The issue turned out to be with the Pylint integrated into the Pytest call.
The parent Pytest call generated a unit testing report, which had empty classnames for additional "empty" tests that Pylint came up with.
SonarQube warned about those empty classnames.
I ended up removing Pylint Pytest integration and just running Pylint as a separate step from Pytest.

share|improve this answer

answered Apr 30 at 21:59

LevLev

2666 bronze badges

add a comment | 

The issue turned out to be with the Pylint integrated into the Pytest call.
The parent Pytest call generated a unit testing report, which had empty classnames for additional "empty" tests that Pylint came up with.
SonarQube warned about those empty classnames.
I ended up removing Pylint Pytest integration and just running Pylint as a separate step from Pytest.

share|improve this answer

answered Apr 30 at 21:59

LevLev

2666 bronze badges

share|improve this answer

answered Apr 30 at 21:59

LevLev

2666 bronze badges

answered Apr 30 at 21:59

LevLev

2666 bronze badges

answered Apr 30 at 21:59

LevLev

2666 bronze badges