while running a feature file I'm getting nothing but 0 Scenarios 0 Steps though all the dependencies were added
image
Related
.net 6 works perfectly for me , but when I create a new project and set .net 7 as a target, I cannot see anything on the screen when I run the project, here is the log :
Creating a new clean layout...
Copying files: Total 105 mb to layout...
Checking whether required frameworks are installed...
Registering the application to run from layout...
Deployment complete (0:00:04.411). Full package name: "8cc8c370-e3bb-40df-a37b-e1408483996c_1.0.0.1_x64__9zz4h110yvjzm"
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Elapsed 00:24.190 ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
========== Elapsed 00:24.192 ==========
First, I think you could restart and update Visual Studio and create a new project to see if it works.
If it doesn't works, I also find a similar issue on Github : MAUI apps crash on launch on Windows after Visual Studio update . You could follow this issue.
The following workaround was mentioned in this issue,
1.Dayjay comments suggests to run app just build as Admin;
2.Redth comments also concludes four ways to solve this issue;
Hope it works for you.
I run semgrep with local yaml rule, but I got the below message which seem block the result, but no obvious error from semgrep:
the result is:
METRICS: Using configs from the Registry (like --config=p/ci) reports
pseudonymous rule metrics to semgrep.dev.
16:38:04 To disable Registry rule metrics, use "--metrics=off".
Running 1 rules...
16:38:04 ran 1 rules on 0 files: 0 findings
The environment is: Linux Docker + python3.6.8 + semgrep0.81.0
I already added "--metrics=off" in the command according its document, is it a bug? It seems this information blocked the scanning (ran 1 rules on 0 files), does anybody know the reason? thanks
Getting this issue while i am Deploy my Asp.net core app on bluemix.
Hosting Provider is Bluemix.
Logs:
Downloading artifacts...DOWNLOAD SUCCESSFUL Target:
https://api.ng.bluemix.net Using manifest file
/home/pipeline/cb3f3db1-2e27-4c5a-a1f4-e5b8f9ada7f6/manifest.yml
Updating app myproject01 in org myproject_org / space Dev as xyz#gmail.com...
OK
Using route myproject01.mybluemix.net
Uploading myproject01...
Uploading app files from: /home/pipeline/cb3f3db1-2e27-4c5a-a1f4-e5b8f9ada7f6
Uploading 14.7M, 2061 files
Done uploading
OK
Binding service myproject01-cloudantNoSQLDB to app myproject01 in org myproject_org / space Dev as katoch.rohit#gmail.com...
OK
Stopping app myproject01 in org myproject_org / space Dev as katoch.rohit#gmail.com...
OK
Starting app myproject01 in org myproject_org / space Dev as katoch.rohit#gmail.com...
-----> Downloaded app package (56M)
ASP.NET Core buildpack version: v0.9-20160706-1603
ASP.NET Core buildpack starting compile
-----> Restoring files from buildpack cache
Copied 199 files from /tmp/cache/.dotnet to /tmp/staged/app
Copied 14925 files from /tmp/cache/.nuget to /tmp/staged/app
Copied 37 files from /tmp/cache/libunwind to /tmp/staged/app
OK
-----> Extracting libunwind
OK
-----> Installing Dotnet CLI
OK
-----> Restoring dependencies with Dotnet CLI
log : Restoring packages for /tmp/staged/app/src/myproject.Utility/project.json...
log : Restoring packages for /tmp/staged/app/src/myproject.Core/project.json...
log : Restoring packages for /tmp/staged/app/src/dotnetCloudantWebstarter/project.json...
log : Restoring packages for /tmp/staged/app/project.json...
log : Writing lock file to disk. Path: /tmp/staged/app/src/myproject.Utility/project.lock.json
log : Writing lock file to disk. Path: /tmp/staged/app/src/myproject.Core/project.lock.json
log : src/myproject.Utility/project.json
log : Restore completed in 1752ms.
log : src/myproject.Core/project.json
log : Restore completed in 1753ms.
log : ./project.json
log : Restore completed in 2036ms.
log : Restoring packages for tool 'Microsoft.AspNetCore.Server.IISIntegration.Tools' in /tmp/staged/app/src/dotnetCloudantWebstarter/project.json...
warn : dotnetCloudantWebstarter (>= 1.0.0) -> System.Threading.Tasks.Extensions (>= 4.0.0-rc2-24027)
log : Writing lock file to disk. Path: /tmp/staged/app/src/dotnetCloudantWebstarter/project.lock.json
log : src/dotnetCloudantWebstarter/project.json
log : Restore completed in 4439ms.
OK
-----> Saving to buildpack cache
Copied 0 files from /tmp/staged/app/.dotnet to /tmp/cache
Copied 0 files from /tmp/staged/app/.nuget to /tmp/cache
ASP.NET Core buildpack is done creating the droplet
-----> Uploading droplet (270M)
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 down
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
0 of 1 instances running, 1 starting
FAILED
Start app timeout
TIP: Application must be listening on the right port. Instead of hard coding the port, use the $PORT environment variable.
Use 'cf logs myproject01 --recent' for more information
Finished: FAILED
plz help me out to get rid of this issue.....
Thanks.
The current versions the boilerplates for ASP.NET Core in Bluemix have had their default memory limits increased to 512MB, but it seems that your application was based on an older version of those boilerplates which had the limit set to 256MB.
While this is enough for a basic "Hello World" style of application, once you start adding more functionality to the application it will need more memory at some point and not having enough memory will cause it to crash.
Increasing the memory limit to 512MB may fix the issues that you're having, but I would also start taking care of the warning messages that you're getting about package version mismatches too before that causes other issues. Pulling packages from both RC2 and RTM in the same application can be problematic when things have changed in the RTM version that your code is trying to call but the package that gets installed is from RC2.
Setup:
Jenkins
NUnit
Selenium
Email-ext (Jenkins plugin)
We have a test suite in C# that does setup: it checks in TestRail for what tests exist in the test plan, and writes to a file that list of tests. The build in Jenkins has two build steps (after pull & build):
Run the setup suite to get the list of tests to bother running.
Run the suite, using the /runlist NUnit parameter to pull in that list.
This works fantastically when there are tests to be run.
However, due to [completely separate implementation], there will be times when that file is empty. Therefore, the NUnit result for the "run with list" build step:
Tests run: 0, Errors: 0, Failures: 0, Inconclusive: 0, Time: 0.010100375885762 seconds
Not run: 0, Invalid: 0, Ignored: 0, Skipped: 0
This tells Jenkins that this step failed:
C:\Program Files (x86)\Jenkins\jobs\[job_name]\workspace>exit 0
Archiving artifacts
Recording NUnit tests results
No test report files were found. Configuration error?
Build step 'Publish NUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure
What I want is one of two things:
At the very least, it would not send out a failure email.
Ideally, the result from the setup build step would tell the build to stop, as there's nothing to build. The "Aborted" email trigger would be sent.
How do I configure Jenkins/this build to have that happen?
I believe I've found an answer to my own question.
Steps:
Install the Conditional Build Step plugin.
Install the Fail The Build plugin.
Add a batch script that returns error code 1 if the tests-to-run file size is 0, or error code 0 otherwise.
Add a single conditional build step:
Execute Windows Batch Commands == the path to the batch file.
Set the build result == Unstable (or whatever).
My batch file code:
#echo off
REM Retrieve the build name.
set arg1=%1
REM Set the file name.
set file="C:\Path\To\TestsToRunFile\%arg1%.txt"
REM Get the file size.
FOR /F "usebackq" %%A IN ('%file%') DO set size=%%~zA
REM Exit codes based on the file size.
IF %size% EQU 0 (
exit /b 0
) ELSE (
exit /b 1
)
Here is the output after the build/web.config transformation:
Copying all files to temporary location below for package/publish:
obj\Release\Package\PackageTmp.
Publishing folder /...
Site was published successfully path_goes_here
========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Publish: 1 succeeded, 0 failed, 0 skipped ==========
yet when it loads the root folder, nothing is there. Going to the site gives a Server Error of
401 - unauthorized: access is denied due to invalid credentials
understandable considering nothing is in that directory, I believe. If possibly misleading.
To work around this issue, I copied and pasted the release of the deployment server to the production server. I didn't have access issues doing this so I don't believe it was preventing me from deploying due to permissions.
How do I troubleshoot this particular scenario?
I tried the following which had worked for other people, hopefully one may work for you:
Publish as release, then go back and publish as debug again.
Publish as web deploy package then go back and publish to filesystem.
Reinstalling VS2012=0 worked until an update upgraded my Publish dialog.
None worked for me though, so the workaround I came up with is to publish as web deploy package - which actually contains the files that would be in the file system folder - get the files (from the PackageTmp folder) and deploy as before.
I found that a DLL reference was missing from one of the projects but I fixed that by adding it, unused, to the start up project, which causes it to be recognised and published.
Hope this helps.
I have tried it with /A:Basic, worked for me
/A:
Specifies the type of authentication to be used. The possible values are NTLM and Basic. If the wmsvc provider setting is specified, the default authentication type is Basic; otherwise, the default authentication type is NTLM.