Recherche avancée

Sur d’autres sites (9470)

• How to debug GitHub Action failure

  9 décembre 2022, par Meltemi

  Just yesterday a stable GitHub Action (CI) started failing rather cryptically and I've run out of tools to debug it.

  


  All I can think of is our BUNDLE_ACCESS_TOKEN went bad somehow but I didn't set that up. It's an Action secret under Repository Secrets that are not visible in GitHub UI. How can I test to see if it's valid ?

  


  Or maybe it's something else ?!? "Bad credentials" is vague...

  


  Here's the meat of the action we're trying to run :

  


  #my_tests.yml
jobs:
  my-test:
    runs-on: ubuntu-latest
    services:
      postgres:
        image: postgres:13.4
        env:
          POSTGRES_USERNAME: postgres
          POSTGRES_PASSWORD: postgres
          POSTGRES_DB: myapp_test
        ports:
          - 5432:5432
        options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5
    env:
      RAILS_ENV: test
      POSTGRES_HOST: localhost
      POSTGRES_USERNAME: pg
      POSTGRES_PASSWORD: pg
      GITHUB_TOKEN: ${{ secrets.BUNDLE_ACCESS_TOKEN }}
      BUNDLE_GITHUB__COM: x-access-token:${{ secrets.BUNDLE_ACCESS_TOKEN }}
      CUCUMBER_FORMAT: progress
    steps:
      - uses: actions/checkout@v2
      - uses: FedericoCarboni/setup-ffmpeg@v1
      ...


  


  And with debug turned on here's the Failure (line 20) from GitHub Actions :

  


  Run FedericoCarboni/setup-ffmpeg@v1

1 ------- ##[debug]Evaluating condition for step: 'Run FedericoCarboni/setup-ffmpeg@v1'
2 ##[debug]Evaluating: success()
3 ##[debug]Evaluating success:
4 ##[debug]=> true
5 ##[debug]Result: true
6 ##[debug]Starting: Run FedericoCarboni/setup-ffmpeg@v1
7 ##[debug]Loading inputs
8 ##[debug]Loading env
9 Run FedericoCarboni/setup-ffmpeg@v1
10   with:
11   env:
12     RAILS_ENV: test
13     POSTGRES_HOST: localhost
14     POSTGRES_USERNAME: pg
15     POSTGRES_PASSWORD: pg
16     GITHUB_TOKEN: ***
17     BUNDLE_GITHUB__COM: x-access-token:***
19     CUCUMBER_FORMAT: progress
20 Error: Bad credentials
21 ##[debug]Node Action run completed with exit code 1
22 ##[debug]Finishing: Run FedericoCarboni/setup-ffmpeg@v1


  


  Thanks for any help.

  


• make/cmake error : relocation R_X86_64_32 against `ff_a64_muxer' can not be used when making a shared object

  21 juin 2017, par NotCras

  Here’s what’s going on. I’m trying to set up OpenSceneGraph, however I run into the following error during the make process (spaces added for easier reading) :

  /usr/bin/ld: /usr/local/lib/libavformat.a(allformats.o): relocation R_X86_64_32 against `ff_a64_muxer' can not be used when making a shared object; recompile with -fPIC
  
  
  
  /usr/local/lib/libavformat.a: error adding symbols: Bad value
  
  
  
  collect2: error: ld returned 1 exit status
  
  
  
  src/osgPlugins/ffmpeg/CMakeFiles/osgdb_ffmpeg.dir/build.make:291: recipe for target 'lib/osgPlugins-3.4.0/osgdb_ffmpeg.so' failed
  
  
  
  make[2]: *** [lib/osgPlugins-3.4.0/osgdb_ffmpeg.so] Error 1
  
  
  
  CMakeFiles/Makefile2:6663: recipe for target 
  
  
  
  'src/osgPlugins/ffmpeg/CMakeFiles/osgdb_ffmpeg.dir/all' failed
  
  
  
  make[1]: *** [src/osgPlugins/ffmpeg/CMakeFiles/osgdb_ffmpeg.dir/all] Error 2
  
  
  
  make[1]: *** Waiting for unfinished jobs....

  This error does not stop the cmake process. A little later (error above occurs at 39%, process fails at 46%), I get this error :

  Makefile:127: recipe for target 'all' failed
  
  
  
  make: *** [all] Error 2

  Then the process stops.

  I’ve looked at some other solutions, but they didn’t have what I needed (here and here). I’ve run cmake with the -fPIC flag and that didn’t solve anything.

  I found a potential solution here but I don’t know how to implement "recompile your FFmpeg/libavcodec/libavformat with pic enabled". Can anyone talk me through it or give me a good resource ? I’ve never done it before and I don’t want to mess up my computer.

  Any help would be much appreciated. Thanks in advance !

• Color spot in FFmpeg output

  2 juin 2022, par Fabian Garcia

  I work in a company that serves multimedia content to different clients and one of these requests that the videos contain the following specifications :

  


  

  • Codec : H264 High@4.0

  


  • Mode : CBR 1 pass

  


  • Window Buffer : 5 secs

  


  • Frame Rate : 29.97/23.97

  


  • Key Frame Interval : 2 secs

  


  • Bitrate : 4000 Kbps

  


  • Size : 1920x1080

  


  • Window Buffer : 5 secs

  


  • GOP : closed

  


  • GOP size : fixed (no scene change detection)

  


  • Window Buffer : 5 secs

  


  • B Frames : As needed

  


  


  For the above, i build following script :

  


  ffmpeg -hide_banner -nostats -loglevel error -y
-init_hw_device cuda=cuda -hwaccel cuda -hwaccel_device cuda
-i 'video_source.mxf' -filter_hw_device cuda
-filter_complex '[0:v]format=nv12,hwupload,yadif_cuda,scale_cuda=1920:1080[v0]'
-map '[v0]' -c:v h264_nvenc -rc cbr -b:v 4M -bufsize 8M -x264-params "keyint=60:min-keyint=48:no-scenecut" -r '30000/1001' -profile:v high -level:v 4
-map 0:1 -c:a libfdk_aac -b:a 96k -ar 44100 -ac 2 -sample_fmt s16
'output.mp4'


  


  The inconvenience is that the generated output presents some color spots in the scene changes (it's a fade) as can be seen in the attached image.

  


  I could notice that in the output video, the time does not match the input precisely, the output is a few milliseconds ahead, I think that the color spot corresponds to the image that should be shown at that moment in the original video.

  


  Can you see something wrong in script ? Or maybe some concept that i don't know is causing a conflict with the output (This is my first time using ffmpeg).

  


  Thank for your help !