I got some errors while generating linux-imx-image.
WARNING: opencv-4.5.2.imx-r0 do_fetch: Failed to fetch URL git://github.com/opencv/opencv_extra.git;destsuffix=extra;name=extra, attempting MIRRORS if available
NOTE: Tasks Summary: Attempted 2831 tasks of which 0 didn't need to be rerun and 2 failed.
Summary: 2 tasks failed: /home/rohan/imx-yocto-bsp/sources/meta-openembedded/meta-oe/recipes-graphics/gphoto2/libgphoto2_2.5.27.bb:do_fetch /home/rohan/imx-yocto-bsp/sources/meta-openembedded/meta-oe/recipes-graphics/tesseract/tesseract_4.1.1.bb:do_fetch Summary: There were 8 WARNING messages shown. Summary: There were 4 ERROR messages shown, returning a non-zero exit code.
I am not sure where the errors and warnings are located.
Related
I am running my UI Tests on Github CI and the tests are flaky. I don't understand how I can fix it. The animations are disabled and I am running the tests on a iPhone 13 plus. A lot of tests are running green, but some are not working. Locally, I got everything working.
These are some logs:
2022-06-21T13:42:23.2627250Z t = 63.34s Tap Cell
2022-06-21T13:42:23.2707530Z t = 63.34s Wait for com.project.project to idle
2022-06-21T13:42:23.2733620Z t = 63.41s Unable to monitor event loop
2022-06-21T13:42:23.2734250Z t = 63.41s Unable to monitor animations
2022-06-21T13:42:23.2734800Z t = 63.42s Find the Cell
2022-06-21T13:42:24.1158670Z t = 64.45s Find the Cell (retry 1)
2022-06-21T13:42:24.1287900Z t = 64.45s Collecting extra data to assist test failure triage
2022-06-21T13:42:24.2022460Z /Users/runner/work/project/UITestCase.swift:665: error: -[project.UserTagTest testTapInTextView] : Failed to get matching snapshot: Lost connection to the application (pid 12676). (Underlying Error: Couldn’t communicate with a helper application. Try your operation again. If that fails, quit and relaunch the application and try again. The connection to service created from an endpoint was invalidated: failed to check-in, peer may have been unloaded: mach_error=10000003.)
It can not find the cell because of these logs:
Unable to monitor event loop
Unable to monitor animations
I know this because I sometimes get different errors than the error above, which says that the connection to the application is lost, right below the Unable to monitor... error logging.
Is there anything I can try? I don't have a reproduction project. This is the command that is executed:
xcodebuild test -project project.xcodeproj -scheme project-iosUITests -destination 'platform=iOS Simulator,name=iPhone 13 Pro,OS=15.5'
The CI runs 35 tests and 5 fails randomly with the Unable to errors. Is there any suggestion to fix this problem?
I have a swift package manager project and I am trying to run unit tests with Fastlane on GitHub actions.
My fastfile looks like
desc('Unit test with spm')
lane :spm_test do
scan(
workspace: ".swiftpm/xcode/package.xcworkspace",
package_path: ".",
device: "iPhone 11",
scheme: SCHEME,
clean: false,
code_coverage: true,
derived_data_path: ".build"
)
end
But time to time I am getting this error,
error: Could not compute signing task inputs - operation was cancelled. (in target 'Scheme_Scheme' from project 'Scheme') - same for multiple dependencies and test target then finally
Testing failed:
Could not compute signing task inputs - operation was cancelled.
Testing cancelled because the build failed.
Last part of build log
3499 ▸ Build Succeeded
3500 2022-04-08 10:53:25.292 xcodebuild[2468:12022] [MT] DVTAssertions: Warning in /Library/Caches/com.apple.xbs/Sources/IDEFrameworks/IDEFrameworks-19466/IDEFoundation/Execution/RunContextManager/IDERunContextManager.m:823
3501 Details: Error deleting scheme: Cannot modify data because the process disallows saving.
3502 Object: <IDERunContextManager: 0x7fdaacb72e50>
3503 Method: -deleteRunContexts:completionQueue:completionBlock:
3504 Thread: <NSThread: 0x7fdaa97170e0>{number = 1, name = main}
3505 Please file a bug at https://feedbackassistant.apple.com with this warning message and any useful information you can provide.
3506 2022-04-08 10:53:25.293 xcodebuild[2468:12022] could not delete old scheme: Error Domain=DVTCustomDataStoringErrors Code=0 "Cannot modify data because the process disallows saving." UserInfo={NSLocalizedDescription=Cannot modify data because the process disallows saving.}
3507
3508 ❌ error: Could not compute signing task inputs - operation was cancelled. (in target 'MyProjectDependency_MyProjectDependency' from project 'MyProjectDependency')
3509
3510
3511
3512 ❌ error: Could not compute signing task inputs - operation was cancelled. (in target 'MyProject_MyProject' from project 'MyProject')
3513
3514
3515
3516 ❌ error: Could not compute signing task inputs - operation was cancelled. (in target 'MyProjectTests' from project 'MyProject')
3517
3518
3519
3520 ❌ error: Could not compute signing task inputs - operation was cancelled. (in target 'MyProject_MyProjectTests' from project 'MyProject')
3521
3522
3523 Testing failed:
3524 Could not compute signing task inputs - operation was cancelled.
3525 Testing cancelled because the build failed.
3526
3527 ** TEST FAILED **
This is running perfectly when I run on my local machine. I have another set of tests that uses a normal Xcode project(not SPM) that also works fine.
What could be the reason for this error and how can I fix it?
UPD: This is happening only with Xcode 13.x, Xcode 12.x is working fine.
I use Specflow with SpecRunner+ I am using the Deafult.srprofile to to re-run failed tests 3 times in visual studio it shows 2passed 1 failed but the status of the test is a failure, the same goes for azure devops if a re-ran test passes the outcome of the run is a failure. The Failures are sometimes caused by locator timeouts or server timeouts not often but saw it happen few time thats why we decided to implement a re-run.
Could anyone help on this?
022-02-09T12:40:13.8607507Z Test Run Failed.
2022-02-09T12:40:13.8608607Z Total tests: 37
2022-02-09T12:40:13.8609271Z Passed: 36
2022-02-09T12:40:13.8609858Z Failed: 1
2022-02-09T12:40:13.8617476Z Total time: 7.4559 Minutes
2022-02-09T12:40:13.9226929Z ##[warning]Vstest failed with error. Check logs for failures. There might be failed tests.
2022-02-09T12:40:14.0075402Z ##[error]Error: The process 'D:\Microsoft_Visual_Studio\2019\Common7\IDE\Extensions\TestPlatform\vstest.console.exe' failed with exit code 1
2022-02-09T12:40:14.8164576Z ##[error]VsTest task failed.
But then the report states that it was retried 3 times which 2 of the retries were seccusefull but still a failure status on the azure devops run.
The behavior of the report is the correct one and sadly this can't be configured to be changed.
What you can do is to adjust how the results are reported back to Azure DevOps.
You can configure it via the VSTest element in the srProfile- File.
This example means, that at least one retry has to be passing:
<VSTest testRetryResults="Unified" passRateAbsolute="1"/>
Docs: https://docs.specflow.org/projects/specflow-runner/en/latest/Profile/VSTest.html
Be aware that we have stopped the development of the SpecFlow+ Runner. More details here: https://specflow.org/using-specflow/the-retirement-of-specflow-runner/
I tried starting parpool in MATLAB 2015b. Command as follows,
parpool('local',3);
This command should allocate 3 workers. Whereas I received an error stating failure to start parpool. The error message as follows,
Error using parpool (line 94)
Failed to start a parallel pool. (For information in addition to
the causing error, validate the profile 'local' in the Cluster Profile
Manager.)
A similar query was posted in (https://nl.mathworks.com/matlabcentral/answers/196549-failed-to-start-a-parallel-pool-in-matlab2015a). I followed the same procedure, to validate the local profile as per the suggestions.
Using distcomp.feature( 'LocalUseMpiexec', false); or distcomp.feature( 'LocalUseMpiexec', true) in startup.m didn't create any improvement. Also when attempting to validate local profile still gives error message as follows,
VALIDATION DETAILS
Profile: local
Scheduler Type: Local
Stage: Cluster connection test (parcluster)
Status: Passed
Description:Validation Passed
Command Line Output:(none)
Error Report:(none)
Debug Log:(none)
Stage: Job test (createJob)
Status: Failed
Description:The job errored or did not reach state finished.
Command Line Output:
Failed to determine if job 24 belongs to this cluster because: Unable to
read file 'C:\Users\varad001\AppData\Roaming\MathWorks\MATLAB
\local_cluster_jobs\R2015b\Job24.in.mat'. No such file or directory..
Error Report:(none)
Debug Log:(none)
Stage: SPMD job test (createCommunicatingJob)
Status: Failed
Description:The job errored or did not reach state finished.
Command Line Output:
Failed to determine if job 25 belongs to this cluster because: Unable to
read file 'C:\Users\varad001\AppData\Roaming\MathWorks\MATLAB
\local_cluster_jobs\R2015b\Job25.in.mat'. No such file or directory..
Error Report:(none)
Debug Log:(none)
Stage: Pool job test (createCommunicatingJob)
Status: Skipped
Description:Validation skipped due to previous failure.
Command Line Output:(none)
Error Report:(none)
Debug Log:(none)
Stage: Parallel pool test (parpool)
Status: Skipped
Description:Validation skipped due to previous failure.
Command Line Output:(none)
Error Report:(none)
Debug Log:(none)
I am receiving these error only in my cluster machine. But launching parpool in my standalone PC is working perfectly. Is there a way to rectify this issue?
I am unable to run the resque-web on my server due to some issues I still have to work on but I still have to check and retry failed jobs in my resque queues.
Has anyone any experience on how to peek the failed jobs queue to see what the error was and then how to retry it using the redis-cli command line?
thanks,
Found a solution on the following link:
http://ariejan.net/2010/08/23/resque-how-to-requeue-failed-jobs
In the rails console we can use these commands to check and retry failed jobs:
1 - Get the number of failed jobs:
Resque::Failure.count
2 - Check the errors exception class and backtrace
Resque::Failure.all(0,20).each { |job|
puts "#{job["exception"]} #{job["backtrace"]}"
}
The job object is a hash with information about the failed job. You may inspect it to check more information. Also note that this only lists the first 20 failed jobs. Not sure how to list them all so you will have to vary the values (0, 20) to get the whole list.
3 - Retry all failed jobs:
(Resque::Failure.count-1).downto(0).each { |i| Resque::Failure.requeue(i) }
4 - Reset the failed jobs count:
Resque::Failure.clear
retrying all the jobs do not reset the counter. We must clear it so it goes to zero.