Codecov is failing to process the code coverage reports. It appears to upload successfully but gives the error: "There was an error processing coverage reports".
My project is already successfully integrated with Travis-CI. I am just trying to post my code coverage reports to Codecov.
It is a public project so it doesn't need a token for Codecov.
I have nothing but a sample test in this project so far. I am trying to make sure this integration works before moving forward.
I have enabled code coverage in the schema editor and when I run the tests in Xcode I can see it is generating code coverage reports.
Do I need to integrate with Slather to format my reports before sending them to Codecov?
Could the paths to my files be wrong?
# travis.yml
language:
- swift
osx_image: xcode10.2
script:
- xcodebuild -scheme Healthy -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone X,OS=12.2' -enableCodeCoverage YES build test
after_success:
- bash <(curl -s https://codecov.io/bash)
2.80s$ bash <(curl -s https://codecov.io/bash)
_____ _
/ ____| | |
| | ___ __| | ___ ___ _____ __
| | / _ \ / _` |/ _ \/ __/ _ \ \ / /
| |___| (_) | (_| | __/ (_| (_) \ V /
\_____\___/ \__,_|\___|\___\___/ \_/
Bash-8a28df4
==> Travis CI detected.
project root: .
--> token set from env
Yaml not found, that's ok! Learn more at http://docs.codecov.io/docs/codecov-yaml
==> Processing Xcode reports via llvm-cov
DerivedData folder: /Users/travis/Library/Developer/Xcode/DerivedData
hint Speed up Swift processing by using use -J 'AppName' (regexp accepted)
hint This will remove Pods/ from your report. Also https://docs.codecov.io/docs/ignoring-paths
+ Building reports for Healthy framework
+ Building reports for HealthyTests xctest
-> Running gcov for Obj-C
==> Running gcov in . (disable via -X gcov)
==> Python coveragepy not found
==> Searching for coverage reports in:
+ .
-> Found 2 reports
==> Detecting git/mercurial file structure
==> Appending build variables
+ TRAVIS_OS_NAME
+ TRAVIS_RUBY_VERSION
==> Reading reports
+ ./HealthyTests.xctest.coverage.txt bytes=768
+ ./Healthy.framework.coverage.txt bytes=417
==> Appending adjustments
http://docs.codecov.io/docs/fixing-reports
+ Found adjustments
==> Gzipping contents
==> Uploading reports
url: https://codecov.io
query: branch=master&commit=a88333de1e49b8ba01ea8afe1106eb4ebab45daf&build=22.1&build_url=&name=&tag=&slug=dcortright%2FHealthy&service=travis&flags=&pr=false&job=215842516
-> Pinging Codecov
https://codecov.io/upload/v4?package=bash-8a28df4&token=[secure]&branch=master&commit=a88333de1e49b8ba01ea8afe1106eb4ebab45daf&build=22.1&build_url=&name=&tag=&slug=dcortright%2FHealthy&service=travis&flags=&pr=false&job=215842516
-> Uploading
-> View reports at https://codecov.io/github/dcortright/Healthy/commit/a88333de1e49b8ba01ea8afe1106eb4ebab45daf
All I am seeing on my Codecov page is "There was an error processing coverage reports".
Related
I need HELP
I have two major errors in creating my first substraste chain (cf. https://substrate.dev/docs/en/tutorials/create-your-first-substrate-chain/setup)
Error in Installing the Front-End Template
~/Bureau/ETH-BIT/substrate/substrate-front-end-template$ ls LICENSE
package.json public README.md src yarn.lock
pclf#ubuntu:~/Bureau/ETH-BIT/substrate/substrate-front-end-template$
yarn install
ERROR: [Errno 2] No such file or directory: 'install'
Error in compiling Substrate
cargo build --release
error: failed to run custom build command for node-template-runtime v2.0.0 (/home/pclf/Bureau/ETH-BIT/substrate/substrate-node-template/runtime)
Caused by: process didn't exit successfully:
/home/pclf/Bureau/ETH-BIT/substrate/substrate-node-template/target/release/build/node-template-runtime-663c8dc25926c960/build-script-build
(exit code: 1) --- stdout Executing build command: "rustup" "run"
"nightly" "cargo" "rustc" "--target=wasm32-unknown-unknown"
"--manifest-path=/home/pclf/Bureau/ETH-BIT/substrate/substrate-node-template/target/release/wbuild/node-template-runtime/Cargo.toml" "--color=always" "--release"
--- stderr
Compiling wasm-build-runner-impl v1.0.0 (/home/pclf/Bureau/ETH-BIT/substrate/substrate-node-template/target/release/wbuild-runner/node-template-runtime4021631938540302808)
Finished release [optimized] target(s) in 7.49s
Running /home/pclf/Bureau/ETH-BIT/substrate/substrate-node-template/target/release/wbuild-runner/node-template-runtime4021631938540302808/target/x86_64-unknown-linux-gnu/release/wasm-build-runner-impl
Compiling sp-arithmetic v2.0.0
Compiling sp-io v2.0.0
Compiling sp-inherents v2.0.0
Compiling frame-metadata v12.0.0
Compiling sp-finality-tracker v2.0.0 error[E0282]: type annotations needed
--> /home/pclf/.cargo/registry/src/github.com-1ecc6299db9ec823/sp-arithmetic-2.0.0/src/fixed_point.rs:541:9
| 541 | let accuracy = P::ACCURACY.saturated_into();
| ^^^^^^^^ consider giving accuracy a type ... 1595 | / implement_fixed!( 1596 | | FixedI64,
1597 | | test_fixed_i64, 1598 | | i64, ... | 1601 | |
"Fixed Point 64 bits signed, range = [-9223372036.854775808,
9223372036.854775807]", 1602 | | );
| |__- in this macro invocation
|
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
error[E0282]: type annotations needed
--> /home/pclf/.cargo/registry/src/github.com-1ecc6299db9ec823/sp-arithmetic-2.0.0/src/fixed_point.rs:541:9
| 541 | let accuracy = P::ACCURACY.saturated_into();
| ^^^^^^^^ consider giving accuracy a type ... 1604 | / implement_fixed!( 1605 | | FixedI128,
1606 | | test_fixed_i128, 1607 | | i128, ... | 1611 |
| [-170141183460469231731.687303715884105728,
170141183460469231731.687303715884105727]_", 1612 | | );
| |__- in this macro invocation
|
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
error[E0282]: type annotations needed
--> /home/pclf/.cargo/registry/src/github.com-1ecc6299db9ec823/sp-arithmetic-2.0.0/src/fixed_point.rs:541:9
| 541 | let accuracy = P::ACCURACY.saturated_into();
| ^^^^^^^^ consider giving accuracy a type ... 1614 | / implement_fixed!( 1615 | | FixedU128,
1616 | | test_fixed_u128, 1617 | | u128, ... | 1621 |
| [0.000000000000000000,
340282366920938463463.374607431768211455]_", 1622 | | );
| |__- in this macro invocation
|
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
error: aborting due to 3 previous errors
For more information about this error, try rustc --explain E0282.
error: could not compile sp-arithmetic
error: build failed
You can just run yarn in the front end template directory, it will work. But where is the "Is LICENCE public" message coming from? You shouldn't see that. Did you clone the substrate-front-end-template repo or just create the directory? The exact process is:
clone it with git clone https://github.com/substrate-developer-hub/substrate-front-end-template
enter folder with cd substrate-front-end-template
run yarn
As for the Substrate compilation error, please downgrade your nightly to an older version, it happens due to a bug in Rust. Here is how to do that:
rustup uninstall nightly
rustup install nightly-2020-10-01
rustup target add wasm32-unknown-unknown --toolchain nightly-2020-10-01
First thing first solve the Substrate compiling first.
run this scrip
https://github.com/substrate-developer-hub/substrate-node-template/blob/master/scripts/init.sh
When you get the node up and running then start using frontend.
maybe somebody can help me.
I, was testing karaf in my local windows laptop an everything work fine. But now I'm trying to install it on Centos Linux server, but Im not getting the same results.
My steps:
1-Donwload Karaf from http://www.apache.org/dyn/closer.lua/karaf/4.2.8/apache-karaf-4.2.8.tar.gz
2- Unzipped in the centos linux path: /usr/local/apache-karaf-4.2.8
3- Check the java version installed in the server
JAVA_HOME=/usr/local/jdk1.8.0_251
PATH=.../usr/local/jdk1.8.0_251/jre/bin..
4- run sudo ./bin/karaf and then
karaf: JAVA_HOME not set; results may vary
__ __ ____
/ //_/____ __________ _/ __/
/ ,< / __ / ___/ __/ /_
/ /| |/ // / / / // / __/
// ||__,// __,//
Apache Karaf (4.2.8)
Anyway the shell become active, but I tried to add features and I receved this error ( It doesn't seem to be related to the previous message)
karaf#root()> feature:repo-add camel
Adding feature url mvn:org.apache.camel.karaf/apache-camel/RELEASE/xml/features
Error executing command: Error resolving artifact org.apache.camel.karaf:apache-camel:xml:features:RELEASE: [Failed to resolve version for org.apache.camel.karaf:apache-camel:xml:features:RELEASE: Could not find metadata org.apache.camel.karaf:apache-camel/maven-metadata.xml in local (/root/.m2/repository)] : mvn:org.apache.camel.karaf/apache-camel/RELEASE/xml/features
I did the same on my PC and everything worked perfectly. Im missing something specific for Linux ? Any Idea?
Thanks in advance
Karaf uses etc/org.ops4j.pax.url.mvn.cfg to list all the m2 repos from where he can downloads your bundles/features.
By default, the value for this distribution is :
org.ops4j.pax.url.mvn.repositories= \
https://repo1.maven.org/maven2#id=central, \
https://repository.apache.org/content/groups/snapshots-group#id=apache#snapshots#noreleases, \
https://oss.sonatype.org/content/repositories/ops4j-snapshots#id=ops4j.sonatype.snapshots.deploy#snapshots#noreleases
However, in your case, it seems it tries to get it from /root/.m2/repository. Could you check your etc/org.ops4j.pax.url.mvn.cfg and see if there is no modification to it ?
I was looking for logging frameworks available in OpenDaylight Controller.
Something similar to ELK stack.
I found apache decanter as a possible way to do this.
https://karaf.apache.org/manual/decanter/latest-1/
The problem is that it works fine with normal karaf shell but doesnt work so with the ODL karaf shell of Oxygen SR4 release.
As per the documentation,
https://karaf.apache.org/download.html#decanter-installation
feature:repo-add decanter
feature:install decanter-appender-elasticsearch
feature:install decanter-collector-log
feature:install decanter-collector-jmx
I tried the same in ODL karaf shell.
I downloaded the Oxygen-SR4 binary and started the karaf shell.
./karaf clean Apache Karaf starting up. Press Enter to open the shell now... 100% [========================================================================]
Karaf started in 0s. Bundle stats: 13 active, 13 total
________ ________ .__ .__ .__ __
\_____ \ ______ ____ ____ \______ \ _____ ___.__.| | |__| ____ | |___/ |_
/ | \\____ \_/ __ \ / \ | | \\__ \< | || | | |/ ___\| | \ __\
/ | \ |_> > ___/| | \| ` \/ __ \\___ || |_| / /_/ > Y \ |
\_______ / __/ \___ >___| /_______ (____ / ____||____/__\___ /|___| /__|
\/|__| \/ \/ \/ \/\/ /_____/ \/
Hit '<tab>' for a list of available commands and '[cmd] --help' for help on a specific command. Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown OpenDaylight.
opendaylight-user#root>system:version
4.1.6
opendaylight-user#root>feature:repo-add decanter Adding feature url
opendaylight-user#root>feature:install decanter-appender-elasticsearch
org.apache.karaf.features.core[org.apache.karaf.features.internal.service.FeaturesServiceImpl] : null
But the same thing works with plain apache karaf shell.
./karaf
__ __ ____
/ //_/____ __________ _/ __/
/ ,< / __ `/ ___/ __ `/ /_
/ /| |/ /_/ / / / /_/ / __/
/_/ |_|\__,_/_/ \__,_/_/
Apache Karaf (4.2.5)
Hit '<tab>' for a list of available commands and '[cmd] --help' for help on a specific command. Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown Karaf.
karaf#root()> feature:repo-add decanter Adding feature url mvn:org.apache.karaf.decanter/apache-karaf-decanter/RELEASE/xml/features karaf#root()> feature:install decanter-appender-elasticsearch karaf#root()>
Can anyone point out what is missing here because I feel the shell versions are similar?
Can you also suggest some other logging frameworks to process Karaf logs and data in OpenDaylight Controller(Oxygen SR4) something similar to ELK stack.
we use decanter in upstream OpenDaylight system testing. the features we
install (using the featuresBoot variable in etc/org.apache.karaf.features.cfg are:
odl-jolokia,decanter-collector-jmx,decanter-appender-elasticsearch
but, we also configure the featuresRepositories to have:
mvn:org.apache.karaf.decanter/apache-karaf-decanter/1.0.0/xml/features
here is a wiki page with some extra info.
here is an example of us grabbing data to find Mem Usage and we also
install elasticsearch which lets us see it as a graph over time
Hope it helps.
I am new to Angular CLI. My background is in C# ASP.NET. I recently spun up a ASP.NET Core app with Angular CLI through the project wizard of Visual Studio. All that I needed to do to get things working on http://localhost:4200 was to run npm install #angular/cli
and then
ng serve
and I was good to go.
To get the latest stable release of Angular, I then ran
ng update
Now, ng serve returns the error "The serve command requires to be run in an Angular project, but a project definition could not be found."
Also, one other observation is that the $schema reference to schema.json from the .angular-cli.json file is no longer available in the path "./node_modules/#angular/cli/lib/config/schema.json". The config folder is completely missing and I've read that it the config folder was eliminated in a previous version.
My question, is how do i change my .angular-cli.json or other project files to conform to the new standard?
Below is a screenshot of my current versions.
C:\Users\andrew.kirby\source\repos\SchoolsList\SchoolsList\ClientApp>ng --version
_ _ ____ _ ___
/ \ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__| | | | | | |
/ ___ \| | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ \_\_| |_|\__, |\__,_|_|\__,_|_| \____|_____|___|
|___/
Angular CLI: 7.3.8
Node: 10.9.0
OS: win32 x64
Angular: 7.2.14
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router
Package Version
------------------------------------------------------
#angular-devkit/architect 0.13.8
#angular-devkit/core 7.3.8
#angular-devkit/schematics 7.3.8
#angular/cli 7.3.8
#schematics/angular 7.3.8
#schematics/update 0.13.8
rxjs 6.5.1
typescript 3.2.4
When I start roo.sh, the command logs a lot of error about the version of libraries and the Roo version:
$ /opt/apps/ggg/spring-roo-2.0.0.RC1/bin/roo.sh
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: com.github.antlrjavaparser.antlr-java-parser:1.0.15
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.commons.codec:1.8.0
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.commons.io:2.4.0
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.commons.lang3:3.1.0
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.fusesource.jansi:1.6.0
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.jsoup:1.9.1
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.aries.subsystem.api:2.0.8
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.aries.subsystem.core:2.0.8
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.apache.aries.util:1.1.1
... More "Auto-deploy" warnings and finally ...
_
___ _ __ _ __(_)_ __ __ _ _ __ ___ ___
/ __| '_ \| '__| | '_ \ / _` | | '__/ _ \ / _ \
\__ \ |_) | | | | | | | (_| | | | | (_) | (_) |
|___/ .__/|_| |_|_| |_|\__, | |_| \___/ \___/
|_| |___/ UNKNOWN VERSION
Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER.
roo>
And if I create a project, the Spring Roo's version in the pom.xml file created is UNKNOWN VERSION:
<properties>
<roo.version>UNKNOWN VERSION</roo.version>
Then, if I fix the file setting the 2.0.0 RC1 version, when I start again the Roo console, it shows me:
...
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: org.springframework.roo.wrapping.snakeyaml:1.15.1
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: slf4j.api:1.7.12
Auto-deploy install: org.osgi.framework.BundleException: Bundle symbolic name and version are not unique: slf4j.jdk14:1.7.12
_
___ _ __ _ __(_)_ __ __ _ _ __ ___ ___
/ __| '_ \| '__| | '_ \ / _` | | '__/ _ \ / _ \
\__ \ |_) | | | | | | | (_| | | | | (_) | (_) |
|___/ .__/|_| |_|_| |_|\__, | |_| \___/ \___/
|_| |___/ UNKNOWN VERSION
Welcome to Spring Roo. For assistance press TAB or type "hint" then hit ENTER.
WARNING: You are using Spring Roo UNKNOWN VERSION, but project was generated using Spring Roo 2.0.0 RC1.
If you continue with the execution your project might suffer some changes.
Do you want to continue opening Spring Roo Shell?(YES/No)
How can I fix this issue with the version? Is there a file where I can setup the version number?
I've saw that you're executing the roo.sh script in the following folder:
/opt/apps/ggg
Do you have admin permissions in that folder? Could you try to execute the roo.sh script inside ~/apps/ggg folder?
Let me know if that helps you.
Regards
I found the problem: Spring Roo uses the name of the folder where is contained to known its own version. After rename the folder /opt/apps/ggg/roo to /opt/apps/ggg/spring-roo-2.0.0.RC1 worked as expected.
I known that the original name in the distribution file downloaded from http://projects.spring.io/spring-roo/ was spring-roo-2.0.0.RC1 (I renamed it when I uncompressed the zip into /opt/apps/ggg), but I never thought that Spring used the folder name to known the version, and to be honest, I never saw a behavior like this, but renaming the folder name solve the problem.
Thanks for the help.