Fix config tests - #2388
Conversation
|
@Kurt-von-Laven can you help me to fix it? It's quite hopeless to have to wait more than half an hour for the 5 tests I want to fix config to run. I'm using certain github variables to resolve the repository name and branch correctly. I'm not sure if I'm doing it right and since I can't debug the values I get as I'm a bit blind. |
|
@bdovaz you can set the following in the commit message when you just update python code and want to reduce the tested methodes |
TEST_KEYWORDS=config_test
|
In a bar, can't act now :/ |
Format all variables
|
@nvuillam @Kurt-von-Laven I give up, I can't find the right combination to correctly resolve the variables for the owner and repository name when coming from a fork. If you help me I would appreciate it Also, this quick build does not work with a test commit I have done and it is even more frustrating to have to wait more than half an hour between tests. |
|
Rollback ? ^^ |
TEST_KEYWORDS=config_test
TEST_KEYWORDS=config_test
TEST_KEYWORDS=config_test
TEST_KEYWORDS=config_test
TEST_KEYWORDS=config_test
|
@nvuillam @Kurt-von-Laven looks like the key was: https://docs.github.com/en/actions/learn-github-actions/contexts Looking at the contents of In this build I have passed the tests only as I had not done rebase I got an error fixed in main: https://github.com/oxsecurity/megalinter/actions/runs/4269559713/jobs/7432816126 I have launched a new build and I hope it is the final one and I can unlock @echoix. |
|
@nvuillam can you solve the checkov problems please? I'm not at home 馃槄 |
Yeah, you can get the repository and branch out of the |
|
@nvuillam but at the end you have merged it without solving checkov errors. I say this because anyone who wants to merge is going to encounter the same problem. |
|
@bdovaz i did it in another PR :) |

Attemp to fix them with the help of @Kurt-von-Laven in #2381 (comment)