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

Lint Error #4

Closed
alan412 opened this issue Sep 24, 2020 · 6 comments
Closed

Lint Error #4

alan412 opened this issue Sep 24, 2020 · 6 comments

Comments

@alan412
Copy link

alan412 commented Sep 24, 2020

The lint error that was in 5.5 is still here in 6.0

See: FIRST-Tech-Challenge/SkyStone#262

@abidingabi
Copy link

To clarify, this isn't an issue with Travis CI; this is an issue that has to do with the lint gradle task. However, this comes up in Travis CI because it likely uses some form of ./gradlew build under the hood, which would invoke the lint gradle task. This also precludes using ./gradlew build from the command line in the FTC SDK.

Any call to the lint task will cause this error however (in this case caused by running ./gradlew lint:

> Task :FtcRobotController:lint FAILED
Ran lint on variant debug: 34 issues found
Ran lint on variant release: 34 issues found
Wrote HTML report to file:///home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/build/reports/lint-results.html
Wrote XML report to file:///home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/build/reports/lint-results.xml

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':FtcRobotController:lint'.
> Lint found errors in the project; aborting build.

  Fix the issues identified by lint, or add the following to your build script to proceed with errors:
  ...
  android {
      lintOptions {
          abortOnError false
      }
  }
  ...

  The first 3 errors (out of 5) were:
  /home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/src/main/res/menu/ftc_robot_controller.xml:39: Error: Should use app:showAsAction with the appcompat library with xmlns:app="http://schemas.android.com/apk/res-auto" [AppCompatResource]
      android:showAsAction="never"
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  /home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/src/main/res/menu/ftc_robot_controller.xml:44: Error: Should use app:showAsAction with the appcompat library with xmlns:app="http://schemas.android.com/apk/res-auto" [AppCompatResource]
      android:showAsAction="never"
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  /home/dansman805/robotics/temp-ftc-sdk/FtcRobotController/src/main/res/menu/ftc_robot_controller.xml:50: Error: Should use app:showAsAction with the appcompat library with xmlns:app="http://schemas.android.com/apk/res-auto" [AppCompatResource]
      android:showAsAction="never"
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~



* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Steps for reproduction:

  1. cd into the sdk's directory from the command line
  2. run ./gradlew lint (or ./gradlew build!)

Note: this was run on Fedora, however I doubt OS would matter here

Now of course, this isn't really an issue if you don't call ./gradlew lint, however this also occurs when you run ./gradlew build, which is the most convienient way to build from the command line and how CI would likely go about doing things.

This can either be fixed by fixing the actual lint errors, or by adding

android {
      lintOptions {
          abortOnError false
      }
  }

to the build.gradle of the affected modules.

Of course, actually fixing the lint errors would seem to be the preferred course of action.

@shaunsingh
Copy link

adding

android { lintOptions { abortOnError false } }

still results in the same lint errors,

however, running ./gradlew build -x lint seemed to work for me

19417Superstellar referenced this issue in 19417Superstellar/FtcRobotController Sep 2, 2021
@alan412
Copy link
Author

alan412 commented Sep 20, 2021

This error is still there in 7.0

@cbrewsky
Copy link

Can confirm, still here in 7.0...

@Windwoes Windwoes closed this as completed Oct 3, 2021
@Windwoes
Copy link
Member

Windwoes commented Oct 3, 2021

This will be fixed in the next release

@Windwoes Windwoes reopened this Oct 3, 2021
e3l added a commit to KuriosityRobotics/freight-frenzy that referenced this issue Oct 31, 2021
@Windwoes
Copy link
Member

Fixed in 7.1

IsaccBarker referenced this issue in IsaccBarker/ARC Jan 25, 2022
Ghostjammer128 added a commit to FTC-14194/FtcRobotController that referenced this issue Feb 15, 2022
Adjusted autonomous code for Pahrump League Meet FIRST-Tech-Challenge#4
tomeng70 pushed a commit to tomeng70/FtcRobotController that referenced this issue Oct 24, 2023
JuliaOstroff added a commit to JuliaOstroff/FtcRobotController that referenced this issue Nov 22, 2023
iFlezy added a commit to 201-991-Broncobotics/FTC-Command-Based that referenced this issue Nov 29, 2023
CRF1234 added a commit to Logical05/FTC that referenced this issue Dec 1, 2023
WCARDO-13415 pushed a commit to ElectricStormRobotics/FtcRobotController that referenced this issue Dec 17, 2023
kinyewlee added a commit to kinyewlee/CenterStage that referenced this issue Aug 6, 2024
rolerbot pushed a commit to rolerbot/cod that referenced this issue Aug 8, 2024
…RST-Tech-Challenge#4)

* actualizare cod cu bratul scurt si pozitii(posibil sa se schimbe)

* Add existing file

---------

Co-authored-by: DavidPav3l <[valid-email]>
Ehicy pushed a commit to FFFabulousRobotics/FtcRobotController that referenced this issue Sep 22, 2024
…tus-check-fix

Change Android CI run setting
Vullarim pushed a commit to BB-Mentor/FtcRobotController that referenced this issue Oct 24, 2024
…er-Direction-Bugfix

Encoder direction bugfix
delmarrobotics pushed a commit to delmarrobotics/intothedeep that referenced this issue Dec 1, 2024
delmarrobotics pushed a commit to delmarrobotics/intothedeep that referenced this issue Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants