|
Ran
|
Jobs
1
|
Files
2
|
Run time
1min
|
Badge
README BADGES
|
push
github
Give both versions the same sign-ins in the benchmarks Two benchmarks named MAX_STORED_SIGN_INS, which 1fa07c2 removed, so the candidate's workers failed with NameError. The others stored each sign-in's PKCE verifier and redirect URI only in omniauth.oauth2, which this gem no longer reads, so the PKCE callback exchanged the code without a verifier, and the two versions didn't do the same work. Store each sign-in in OmniAuth's omniauth.sign_ins, with its origin and verifier, and in omniauth.oauth2 too, so a baseline from before 1fa07c2 finds it. Run the benchmarks with the most sign-ins with 3, the most OmniAuth 2.4 keeps, as a number both versions share. Reported in https://github.com/omniauth/omniauth-oauth2/commit/6dcb2dfc5#commitcomment-210020968
32 of 32 branches covered (100.0%)
Branch coverage included in aggregate %.
117 of 117 relevant lines covered (100.0%)
26.6 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 43611645043.1 | 2 |
100.0
|
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|